Testing Knowledge ShareNet 2011

Introduction / Objective of the Abstract Abstract Type: Poster Title: Risk

Based Testing Strategy for SOA Testing

Introduction:

Risk-based testing (RBT) is a type of software test strategy that prioritizes the features and functions to be tested based on the risk they represent, a function of their importance and likelihood or impact of failure.

Objective:

RBT may be useful for projects where testing is always under pressure and/or where requirements keep changing/ additional CRs late in the testing cycle and/or where the requirements contain multiple components for e.g., suite of web services where each web service has to be tested in a given release.

Submitted By:Provide complete details of submitter. Name Suresh Pisupati Location Hyderabad Contact details 9603095085 (Mobile) 040-67378574 ( Office) Notes ID : Suresh Pisupati/India/IBM@IBMIN Short ID :supisupa etc

Testing Knowledge ShareNet 2011 Details of the Abstract (Methods / Approach / Description / Actual steps of implementation etc..)

Why Risk based testing? Testing is the last phase of the Software development life cycle and will be always under pressure to meet the deadlines. The main idea of the Risk based testing is to find critical defects in the early stage of the test life cycle. How a Risk based testing is implemented? In Risk based testing, all the Risks has to identified in the first phase of testing life cycle and all the tests have to be prioritized based on Business Importance and Technical Impact of the requirements. Unique characteristics: Critical Defects will be uncovered early in the test life cycle which leaves very little chance for a code break in the later stages. RBT will increase the onset of defects in the initial weeks of test cycle compared to traditional test approach.

Results and Benefits observed after implementing the Idea

Benefits to Client: reducing the cost of the project test phase future potential production costs will be reduced by optimizing the test process Cost of fixing defects will be reduced Benefits to Testers: Entire Test suite can be optimized and streamlined effectively as the critical defect fix impacts will be done early in the test cycle. Reusability: RBT can be deployed and the metrics can be tracked in a pool of different projects to measure the potential benefits. RBT if found successful can be institutionalized across the sector(s) if applicable.
Key Milestone Achieved :-

RBT has been successfully implemented in Agile Project with SOA Testing and this could help to broaden the offshore scope of engagement from 27% to 95% as on today spanning about 5 releases in a duration of one year.

Improved Test Metrics. Reduced Defect Leakage

------------------0--------------------

Testing Knowledge ShareNet 2011