1. Maintaining Quality Test Optimization with Increasing Software Complexity
Ankit Goyal
Software Engineer II
Adobe Systems

2. Agenda
1.Overview 2.Need For Quality Test Optimization 3.Methods to Develop Quality Test Optimization - Reusability Risk Based Testing(RBT) -Defect Management Process(DMP)

3. Abstract
This paper describes about Maintaining Quality Test Optimization with Increasing Software Complexity.
It describes several methods to support and enhance testing process so that the complex software can be tested properly and delivered within the given time interval.
There are a lot of different domains that have grown up in the last several decades like e-commerce, education, banking sector etc., so there is a need for testing software on these domains and potential Variables associated with them. But to test them, the time to test has not proportionally gone up. There arises the need to test these new variables and parameters associated with the software within the testing time scheduled.

4. Need For Maintaining Quality Test Optimization
The Development Life Cycle of building product is quite complex in which each and every intermediate deliverable contains some certain quality attributes that affect the quality of the end product to be delivered.
Achieving 100% quality product is quite a difficult task and if the software is more complex then more effort is required to perform in each stage of Product Development Life Cycle.
A highly matured process quality is required in order to achieve a predictable end quality product.
Since testing process is the last stage before release of the product to the customer, it definitely holds the key to Success of the end product in market.

5. Methods To Develop and Maintain Quality Test Optimization
Reusability
Re-using of test cases, scenarios, artifacts, data etc. from previous projects that can be applied on current releases
Useful to save time when we have to work on lot of Combinations.
Testing communities need to make a repository where the testers can save their test scenarios, cases etc. from the previous releases so that they can be used for the next upcoming releases

6. Architecture of Reusability
Testers can search/retrieve their test scenarios/cases from the repository depending on their need. Any modification is done through new creation/storage which again gets saved in Repository.

7. Real Time Example
By reusing the data through previous releases, we can save our ample amount of time and effort as well.

8. Risk Based Testing (RBT)
The type of Software testing that primarily focuses on prioritize the tests of features and functions based on risk of probability of finding the failures.
We can prioritize our test cases/scenarios (High, medium and low) in terms of the Risks associated with testing that scenario.
It will help in finding the bugs associated in the earliest phase of Test Implementation and Execution and will save a lot of time.

9. Implementing RBT from Project Initiation Phase

10. Risk Based Testing Approach
The testers need to build a list of combinations on a sheet to test upon and keep on updating and monitoring that sheet to make sure it is in accordance with latest updated technology.
Testing organization should work on prioritizing the list based on the release they are working on and the end users they are working upon.
Building such a prioritized list is very useful to ensure the right test coverage and within the limited amount of time.

11. Defect Management Process (DMP)
Defect Management is also an important area where we can pay attention, it must be incorporated in each phase of Product development life cycle.
It mainly focuses on preventing defects, finding the defects at the earliest stage of execution process which ultimately reduces time and make developers fix defects at the earliest and not at the final point of release.
Test management team should find out the larger best practices and protocols around defect management and should allow the tester to use his/her creativity in reporting and finding defects.

12. Steps Followed in Defect Management Process

13. Steps Followed in Defect Management Process
Defect Prevention
It involves analyzing defects that were encountered in the past and taking specific actions to prevent the occurrence of those types of defects in the future.
Deliverable Baseline(Quality Gating)
It involves defining Entry and Exit criteria for each and every phase that should be followed in order to avoid defects in deliverables.
Entry criteria:
Test sign off received.
Code Deployment and Environment Readiness.
Business Requirements/Functional Specifications document approved.
Exit criteria: 
No major/critical severity issues are pending resolution from any previous testing stages.
Test environment has been cleaned up for the next release..

14. Steps Followed in Defect Management Process
Defect Discovery
It involves finding defect as soon as possible because when we move in the later phase of product development cycle, the cost of a software defect goes up.
For e.g. Defects discovered in design/analysis phase have less impact than that discovered in implementation phase.

15. Steps Followed in Defect Management Process
Defect Resolution Process
Prioritize Risk – It determine the importance of fixing a particular defect. 
Schedule Fix and Fix defect – It defines the timeline to fix a defect. Based on the priority of the defect, the fix should be scheduled.
Report Resolution -- It notifies all relevant parties how and when the defect was repaired. Once the defect has been fixed and the fix verified, appropriate developers, users, and testers must be notified that the defect has been fixed along with other pertinent information.

16. Steps Followed in Defect Management Process
SLA(Service Level Agreement) for the type of defect involving its problem type and the resolution time period defined.

17. Steps Followed in Defect Management Process
Process Improvement
A method of improving the way a discrete set of business activities is improvements to the current systems based upon the analysis of what actually was the reason for the problem/ organized and managed.
Involves finding out what all reasons could be there for a particular problem as even a minor defect represents an opportunity to learn how to improve the process and prevent potentially major failure. Fish Bone analysis plays an important role in process improvement.
Management Reporting
The management reporting mainly involves reporting of Value Add, NVA (Non Value Add) defects, DRE (Defect Removal Efficiency), Defect Density etc.

18. Metrics
The diagram shows the NVA and VA metrics in a Quarter having 4 Projects.

19. About the Author
Ankit Goyal is working as Software Engineer (II) In Adobe Systems (Noida). He has 6 Years of experience in White Box and Black Box testing. He is an IT Engineering Graduate from JMIT College (Kurukshetra University). He is currently working in Creative Cloud project. Ankit is an ISTQB certified tester. He can be contacted at

20. Questions??

21. Thank You!!!