Thursday, March 11, 2010

Testing Activities in a Test Process following RUP + Agile methhodology

Here is a list of Test Activities to be carried out in a Test Process following RUP+Agile Methodology.

Background: A new testing team will carry out the testing of product say ABC 6.0 where as the previous release ABC 5.0 was tested by some other team and very basic info is passed from the previous team to current team.

Inception Phase
• High level Test Strategy will be prepared
• Level-0 estimate from QE side will be provided

Elaboration Phase
• Test Plan will be prepared
• Detailed estimate for Elaboration phase from QE side will be provided
• Base test cases for ABC 5.0 will be made ready
• Base test automation scripts for ABC 5.0 will be made ready
•Functional Testing
oHigh level Functional test scenarios creation referring to the Use case document will be prepared. Test scenarios based on workflows, covering one or more requirements will be created
oTest cases from the Test scenarios will be derived in iteration wise as an when design document and UI screenshots for the particular feature is available
oBase setup of Test environment for ABC 5.0 will be made ready
•Performance Testing
To ensure validity in comparisons of ABC 6.0 performance to its baseline, the performance testing methodology would include to be executed on ABC 5.0 to refresh past performance test results as the application is expected to function with client's user volume of data or Match the
testing methodology used for the ABC 5.0, so that those tests can be used as a baseline
o Analysis of ABC 6.0 requirement will be carried outo Performance Test Plan will be prepared
o Test environment for ABC 5.0 will be prepared
o Test Scripts will be prepared
o Base Line testing for ABC 5.0 will be carried out and parameters will be defined and finalized for comparison.

Construction Phase
• Test Plan will be updated/modified with execution plan.
• Detailed estimate for Construction phase from QE side will be provided
• Functional Testing
Assuming that all the new requirements part of ABC 6.0 would be delivered to QE in a number of iterations, following activities would be carried out on each of the iteration, Iteration 1 to N as defined by the team for the short releases.
o Test Case writing will be completed. Test cases would be organized as Smoke / Priority 1 / Regression test cases
o Traceability matrix from Requirement to Use Case to Test Cases will be createdo In each iteration, all the test cases authored will be sent to the stakeholders or their representatives for reviewo Setting up of the Test Environment during iteration wise testing will be carried out by deploying the build provided by Development team on top of ABC 5.0.
o Functional test cases would be executed to validate each requirement implemented correctly or not.
o Test Scripts for Automation would be prepared. Focus will be given on continuous creation of automated tests covering all Functional and Regression test cases.
o Automated test scripts will be executed
o After testing the new features, Regression testing is planned at the end of each iteration to ensure that defects fixed during the current iterations did not regress the producto Defect will be reported as part of Functional and Regression Testing
o All the fixed defects will be verified in the new build before going for the new feature testing. Sev1 and Sev2 defects must be planned to get fixed in the current iteration.o Test cases and Test Scripts will be modified as required .
o Test Plan will be reviewed at the end of each iteration to investigate incomplete tasks and re-estimate the timelines, if required
o Document validation with respect to the feature – User Manual, Online help, Installation Guides, Configuration, and Read Me File, Labeling and Packaging will be validated.o Project meeting will be conducted every day where the entire team sits together and discusses about the progress of the project and any issues preventing the progress.
o At the end of each iteration, produce Iteration Summary report with metrics to measure progress like
• No. of Test cases run at each iteration
• The running and tested feature metrics
• Effort Planned Vs Actual
• No. of Defects Vs functionality
• Schedule Variance
• Total No. of Test cases executed / Passed / Failed/ Blocked / Not Run
o There will be a Post Iteration Review after each of the iteration and the feedback will be taken as input for the next iteration plan.
Performance Testing
Performance testing will be carried out on iterative basis as on when Functional Testing for a particular feature is completed to ensure that the system performance does not degrade.
o Test Environment Setup ABC 6.0 and deployment of the build.
o Performance testing executiono Analysis, Monitoring and comparison report on performance parameter will be produced on each iteration

Transition Phase
• Test Plan will be updated/modified with further details
• Detailed estimate for Transition phase from QE side will be provided
• Functional Testing
Hardening /Regression iterations are planned to make sure system is stable and the fix does not have any adverse effect on the systemo In the final iteration QE team would test all new requirements and one complete flow as part of regression testing.
o During the final iteration, Regression test cases will be executed on test environment. Automated Regression test suite will be run as part of this.
o Validation of the defects which will be fixed in this phase will be carried out.
o Release note will be validated. Release note mentions the requirement items coded, defects fixed, known issues and any other critical information required for testing
o At the end of the iteration, produce Iteration Summary report with metrics to measure progress like
• No. of Regression Test cases run at each iteration
• Effort Planned Vs Actual
• No. of Defects Vs functionality
• Schedule Variance
• Total No. of Test cases executed / Passed / Failed/ Blocked / Not Run
• Integration Testing
Integration testing will be carried out in the integration lab to ensure the proper integration of all components of the product.
Performance Testing
Performance testing will be carried out after the regression testing is completed.
o Clean Test Environment Setup ABC 6.0o Performance testing executiono Analysis, Monitoring and comparison report on performance parameter will be produced at the end of the testing.

No comments:

Post a Comment