Unit Testing
- Done alongside Coding, by Developer
- Bolstered by Tester who composes Test Cases guaranteeing 100% Design Coverage
- Unit Test Cases and Unit Testing results should be audited
- Uncertain significant imperfections (according to need and seriousness) are not left
- All Unit Tests are computerized
Incorporation Testing
- Done alongside Continuous Integration as the Sprints progress
- Done toward the end after all the Sprints are finished
- Every single Functional Requirement are tried
- All Interfaces between Units are tried
- All the Defects are Reported
- Tests are robotized where conceivable
System Testing
- Done as the Development advances
- Clients Stories, Features and Functions are Tested
- Testing done in Production Environment
- Quality Tests are executed (Performance, Reliability, and so forth.)
- Deformities are accounted for
- Tests are robotized where conceivable
Client Acceptance Testing
- Done toward the finish of each Sprint and toward the finish of the venture
- Done by the Customer. Criticism is taken by the Team
- Criticism will be a contribution to resulting Sprints
- Client Stories in a Sprint are pre-checked to be testable and are with characterized Acceptance Criteria
Test Types
- Segment Tests (Unit Tests)
- Useful Tests (User Stories Tests)
- Non-useful Tests (Performance, Load, Stress, and so on.)
- Acknowledgment Tests
Tests can be completely Manual, completely Automated, Combination of Manual and Automated or Manual bolstered by Tools.
Bolster Programming and Critique Product Tests
Tests can be for −
- Supporting Development (Support Programming) − Support Programming Tests are utilized by the Programmers.
- To settle on what code they have to write to achieve a specific conduct of a System
- What Tests should be pursued Coding to guarantee the new Code doesn't hamper the remainder of the practices of the System
- Confirmation just (Critique Product) − Critique Product Tests are utilized for finding deficiencies in the completed Product
Business Facing and Technology Facing Tests
To settle on what tests to be performed when, you have to decide if a test is −
- Business Facing, or
- Innovation Facing
Business Facing Tests
A Test is a business-confronting test in the event that it responds to the inquiries surrounded with words from business area. These are comprehended by the business specialists and would intrigue them so conduct of the framework can be clarified in the ongoing situation.
Innovation Facing Tests
A Test is an innovation confronting test in the event that it addresses the inquiries encircled with words from innovation area. The software engineers comprehend what should be actualized dependent on the explanations on innovation.
These two parts of test types can be seen utilizing the Agile Testing Quadrants characterized by Brian Marick.
Agile Testing Quadrants
Consolidating the two parts of Testing Types, the accompanying Agile Testing Quadrants are determined by Brian Marick −
The Agile Testing Quadrants give an accommodating scientific classification to help groups recognize, design and execute the testing required.
- Quadrant Q1 − Unit Level, Technology Facing, and supports the designers. Unit tests have a place with this Quadrant. These tests can be Automated tests.
- Quadrant Q2 − System level, business confronting, and adjust item conduct. Utilitarian tests have a place with this quadrant. These tests are either manual or mechanized.
- Quadrant Q3 − System or User Acceptance Level, Business Facing and spotlight on continuous situations. Client Acceptance Tests have a place with this quadrant. These tests are manual.
- Quadrant Q4 − System or Operational Acceptance Level, Technology Facing and Focus on Performance, Load, Stress, Maintainability, Scalability Tests. Extraordinary instruments can be utilized for these tests alongside mechanization testing.
