While following risk based test approach any change made in the product are analyzed as a potential risk. Appropriate Risk assessment is done by using any or all of the below techniques:
brainstorming contacting domain/subject matter experts lessons learnt from previous projects/maintaining checklists(Risk register) Analysis of customer escalations vs components (code commits).
Depending upon the risk rating, areas are prioritized and risk response is designed by identifying the test coverage in each area. All product components are evaluated to identify the degree of impact introduced by the change (bug fix/new feature).
Exploratory testing would be targeted on high risk areas to identify bugs early in the test cycle followed by test suite runs.
High priority Breadth tests would be executed to cover mostly used features of the product, followed by other tests run for coverage and confidence.
Depth tests are run to test the functionality in detail, this is applicable for new features and for redesigned components.
For example, to cover regression, Breadth testing would be done first followed by Depth testing of the changed functionality.
‘Pass/Fail’ Criteria
Each Test Item in the scope will be assigned a Pass or Fail state dependent on two criteria:
Total number and severity of Bugs in an Open & Unresolved state within Bugzilla.The level of successfully executed test for the requirements.
The combination of both criteria will be used to recognize the Test Item can be declared Test Complete.
Comments