Software Testing - Simple Explanation
Phases of Software Testing
1. Static Testing:
- Done without running the code.
- Reviews documents like requirements to catch mistakes early.
2. Unit Testing:
- Tests small parts (functions or methods) of the software.
- Helps make sure each piece works by itself.
3. Integration Testing:
- Tests how different parts work together.
- Checks for issues in how software units connect.
4. System Testing:
- Tests the entire system as one complete product.
- Independent testers do this to make sure it meets client needs.
5. Acceptance Testing:
- Final test before release.
- Checks if users are happy with how it works.
Roles in a Testing Team
Software Testing - Simple Explanation
1. QA Leader:
- Manages the testing team and process.
- Communicates with other teams and tracks progress.
2. Test Lead:
- Understands the system well.
- Helps the team and stays updated with latest tools.
3. Test Engineer Types:
a) Usability Test Engineer - Focuses on how user-friendly the software is.
b) Manual Test Engineer - Runs tests manually.
c) Automated Test Engineer - Uses tools to automate tests.
4. Network Test Engineer:
- Tests performance and handles stress/load testing.
5. Test Library Specialist:
- Manages test scripts, versions, and builds.
6. Tester:
- Designs and runs tests.
- Reports problems to developers and follows testing rules.