Agile Testing Levels and Quadrants

Agile testing levels

Levels of Testing

1. Unit testing – individual unit or feature testing
1. Short program fragment
2. Binary outcome
3. Save cost effort for debug defect
4. Detect bugs at early stages
5. Routine operations reduce the manual testing efforts
2. Integration testing – combine individual unit as group and test
1. Expose the fault at combine unit
2. Tests runs faster
3. Higher code coverage
4. Reliable and easy
5. Catch system level issues like broken DB schema etc
3. System testing- complete application or software
1. Black box testing – functional level
2. White box testing
3. Tests full software product
4. Acceptance testing – software testing for acceptability, acceptable for delivery or not
1. Black box system tests- represent business owners for acceptance
2. Used as regression tests
3. Occurs earlier and more frequently

 

Using cucumber with selenium for automation

 

Agile Testing quadrant

 

Business facing

Quadrant 1 Automated and manual Functional tests	Quadarant 2 Manual Exploratory testing scenarios Usability testing
Quadrant 3 Automated Unit tests Component tests	Quadrant 4 Tools Performance and load testing security testing

 

Quadrant 1

1. Unit level
2. Develop test cases- technology facing
3. Supports developers
4. Perform unit and component testing

Quadrant 2

1. System level- perform manual testing
2. Business facing- test cases
3. Conform product behavior

Quadrant 3

1. System acceptance level – provide feedback of two quadrant
2. Business facing
3. Focus on real time scenarios
4. Perform manual testing- exploratory testing, user testing, collaboration testing

Quadrant 4

1. Operational acceptance level
2. Focuses on
1. Performance
2. Load
3. Stress
4. Maintainability
5. Scalability tests