Agile Testing Quadrants

Combining the two aspects of Testing Types, the following Agile Testing Quadrants are derived by Brian Marick −

The Agile Testing Quadrants provide a helpful taxonomy to help teams identify, plan and execute the testing needed.

Quadrant Q1 − Unit Level, Technology Facing, and supports the developers. Unit tests belong to this Quadrant. These tests can be Automated tests.

Quadrant Q2 − System level, business facing, and conform product behavior. Functional tests belong to this quadrant. These tests are either manual or automated.

Quadrant Q3 − System or User Acceptance Level, Business Facing and focus on real time scenarios. User Acceptance Tests belong to this quadrant. These tests are manual.

Quadrant Q4 − System or Operational Acceptance Level, Technology Facing and Focus on Performance, Load, Stress, Maintainability, Scalability Tests. Special tools can be used for these tests along with automation testing.

As in the case of Traditional Testing, Agile Testing also need to cover all the Test Levels.

Ø  Unit Testing

Ø  Integration Testing

Ø  System Testing

Ø  User Acceptance Testing

Ø  Unit Testing

Done along with Coding, by Developer

v  Supported by Tester who writes Test Cases ensuring 100% Design Coverage

v  Unit Test Cases and Unit Testing results need to be reviewed

v  Unresolved major defects (as per priority and severity) are not left

v  All Unit Tests are automated

Integration Testing

v  Done along with Continuous Integration as the Sprints progress

v  Done at the end after all the Sprints are completed

v  All Functional Requirements are tested

v  All Interfaces between Units are tested

v  All the Defects are Reported

v  Tests are automated where possible

System Testing

      Done as the Development progresses

      Users Stories, Features and Functions are Tested

      Testing done in Production Environment

      Quality Tests are executed (Performance, Reliability, etc.)

      Defects are reported

      Tests are automated where possible

User Acceptance Testing

·         Done at the end of each Sprint and at the end of the project

·         Done by the Customer. Feedback is taken by the Team

·         Feedback will be an input to subsequent Sprints

·         User Stories in a Sprint are pre-verified to be testable and are with defined Acceptance Criteria

Test Types

·         Component Tests (Unit Tests)

·         Functional Tests (User Stories Tests)

·         Non-functional Tests (Performance, Load, Stress, etc.)

·         Acceptance Tests