Efficient Test Practice Reduces Cycle Time by 60%


Published on

STAG’s re-engineering of test practices and process standardization drives tangible benefits for a global leader in wireless communication, enabling it to achieve 60% reduction in testing cycle time and 30% increase in productivity.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Efficient Test Practice Reduces Cycle Time by 60%

  1. 1. CASE STUDYEfficient Test Practice ReducesCycle Time by 60% STAG’s re-engineering of test practices and process standardization drives tangible benefits for a global leader in wireless communication, enabling it to achieve 60% reduction in testing cycle time and 30% increase in productivity. Domain/Category - Technology - C++, PERL Mobile / Wireless TelecomCUSTOMER AND PRODUCT BACKGROUNDThe customer is the India Development Center (IDC) of a world leader in 3G and next-generation mobile technologies.The product in question was a video sharing application that was developed at the IDC using C/C++. The application wasintended for sharing or storing videos on mobile phones with or without Packet Switched (PS) / Circuit Switched (CS) calls.The application used Session Initiation Protocol (SIP) for signaling and Real Time Protocol (RTP) for streaming.PROBLEM STATEMENTThe product components from different development centers were integrated at the IDC and then sent out for field-testingat an overseas site. The client discovered that the field-testing QA team spent considerable amount of time detectingsystem-level defects, leading to an increase in field testing effort and, therefore, delays in product release. The client soughtthe help of a specialist partner to fix this anomaly immediately and arrest defect escapes to field.
  2. 2. SOLUTIONThe STAG team conducted a quick analysis of the existing testprocess and made the following observations: # Test cases added: 340• Test cases documented were not exhaustive and repeatable. # PERL scripts created: 25• Defects observed were not systematically analyzed. (average lines of code per script – 150)• 40% of total defects logged were at the unit level.• The IDC team spent precious time uncovering system level defects.The STAG team first set up a pragmatic test practice to formally design and document test cases based onspecifications/standards for the features to be implemented in every release (weekly) for testing. Clear gate criteria wereimplemented using sanity tests that ensured good test readiness.The team introduced the concept of build and release notes, which helped the IDC test team focus, prioritize the testing tasks,and provide essential timely feedback to the development team for quick and measurable progress in product development.The team added test cases and executed them incrementally for every release. It applied black box techniques and HBT-basedBeST techniques to design test cases. The test cases were developed for both the ‘use’ as well as ‘abuse’ aspects. The team alsodeveloped PERL scripts to detect defects at the SIP level.The STAG team also set up unit testing practices for key components before releasing the build for system testing. It usedEthereal and log testing tools to detect, localize, and capture protocol issues and attach them with the defects logged to helpthe development team fix the code quickly.The team also tracked defects and mapped them to the features, modules, and developers to enable quick resolution. Afterevery release, the team generated a test report that gave clear directions for taking the required corrective actions.OUTCOME AND VALUE ADDITIONSSetting up unit level testing resulted in reduction of defects in system testing and eliminated the occurrence of the same defecttypes in different features. Reduced rework in coding as well as test execution resulted in a 30% increase in productivity. Also,there was a 90% reduction in network independent system level defects to field testing.The defect identification and fixing cycle was brought down to 2 days from 5 days. Zero defect escape to field contributed toreduction in field testing cycle to 1 day from 3 days for every release. The average defect count reduced from 20 to 12 perrelease.Overall, as the focus of defect detection moved from unit level to system level, the testing cycle was reduced to 3 days from 5days. CUSTOMER SPEAK …We are very pleased with our association with STAG, as they brought about a transformation in our test practices. This resulted in a 60% reduction in testing effort, a 66% reduction in the field testing cycle, and a 30% saving from manpower reduction. - QA Manager Visit: www.stagsoftware.com | E-mail: marketing@stagsoftware.com Bangalore: +91 80 28495574 / 41263009 | Chennai: +91 44 4214 3469 / 2442 0396 2013 © STAG Software Private Limited. All rights reserved. HBT is the IP of STAG Software Private Limited. All trademarks are acknowledged.