How we test tvideo at skype
Upcoming SlideShare
Loading in...5
×
 

How we test tvideo at skype

on

  • 4,518 views

 

Statistics

Views

Total Views
4,518
Views on SlideShare
3,170
Embed Views
1,348

Actions

Likes
0
Downloads
13
Comments
0

7 Embeds 1,348

http://www.qaclubkiev.com 1317
http://www.ciklum.com 18
http://careers.ciklum.com 4
http://ciklum.com 3
http://www.ciklum.net 3
http://5581279924305827301_55eaa25a798f49483b4dfafbabff5c5a57e907be.blogspot.com 2
http://ciklum.net 1
More...

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

How we test tvideo at skype How we test tvideo at skype Presentation Transcript

  • How we test Video at SkypeApril 2012
  • Oksana Dementsova• SDET, Video in Tallinn office• Microsoft Platforms Team oksana.dementsova Slide 2
  • Agenda1. Skype Video Team2. How we develop Video3. How we test Video 2011 © Skype. Commercially confidential. Slide 3
  • Video Team Slide 4
  • Video Team• Video Team develops Skype Video functionality (Video Library)• Structure: • Video Developers team: 18 Developers • Video QE team: 9 Quality Engineers (QEs)• Location: Tallinn and Stockholm Slide 5
  • Development process Slide 6
  • Video Library• Platform • Microsoft Platforms • iOS, OSX Platform • Embedded and Android• Streaming• Codec, processing Slide 7
  • Video Library release• RV – collection of functionality that provides an end user or third party a complete set of functionality that is valuable in the market.• RVs at Skype: Video, Audio, iPhone UI, Call Signalling• Release of Video Library each 2 months• Important fixes are backported to the release• Other RVs (release vehicles) consume last released Video Library during development Slide 8
  • Development processes• Scrum teams of 2-5 developers, 1-2 QEs• Sprint length: 2 weeks• QEs tasks in Scrum: • Adding Acceptance Criteria to Product Backlog Items (PBIs) • Creating Testing Product Backlog Items (PBIs) • Taking part in task estimation • Working on task during the Sprint • Reporting on quality status during Sprint review Slide 9
  • What else does Video QE do?• We own the product we develop• We are responsible for quality• We make the product quality status visible• We are a communication channel between user and developers• Technology scouting Slide 10
  • QE Team Communications• Why? To share knowledge, update the status outside Scrum team, to get the idea of Video Library status• How? Skype chats; Video calls; Face to face communication; Offsites; Presentations; workshops• When? Weekly PPP (Progress, Problems, Plans) update; Weekly Video QE meeting; Video QE summits, Video team offsites Slide 11
  • Testing process Slide 12
  • Tools used for test planning and reporting• Bug tracking system: Jira• Test repository: TMT• Documentation, reporting system: Confluence Slide 13
  • Testing metrics for real time video• Objective: • Frame rate • Resolution and aspect ratio • Color space • Bitrate • Delay• Subjective: • Smoothness, jerkiness, freezes • Sharpness, pixelation, artifacts, flickering Slide 14
  • Objective testing• Logs• Call technical info Slide 15
  • Subjective testing• Visually• Call quality feedback• Labs Slide 16
  • Types of testing• Manual and automatic• Unit, Component, system, integration• Functional and non-functional (NFR – non-functional requirements)• Performance• Integration: Exploratory, Smoke, Interoperability Slide 17
  • After integration Slide 18
  • Smoke testing Slide 19
  • Functional testing• Does it work? Slide 20
  • Non-functional testing• How does it work? Slide 21
  • Interoperability testing Slide 22
  • Performance testing Slide 23
  • Release testing• Build configurations• Release testing matrix for Windows desktop: Slide 24
  • Tools we use Slide 25
  • Automatic calling system (ACS)• Internally developed• Hundreds of computers in Tallinn and Stockholm offices, a lot of individual machines over the world Slide 26
  • Automatic calling system (ACS)• Runs thousands automatic 1:1 and conference calls every day on different platforms. Test reports provided• Testcases: number of calls, their duration, idle time, participants, build version, video input device (camera or screen sharing) Slide 27
  • Client logging• Should be enabled• Logs are encrypted• Internal tool which allows: • Decrypting logs • Parsing logs • Saving logs Slide 28
  • Parsing the log files• Example of Windows Phone log lines parsing Slide 29
  • Helpful tools• Network emulating tools: Dummynet• Tools to load the PC: CPU killer, CPU burn• Virtual cameras Slide 30
  • Helpful Windows Phone tools• Bugsense• Internal tool for saving call stack• zSystemInfo Slide 31
  • Thank you! Questions? Slide 32