- Smoke or Sanity
** Non-extensive software testing, makes sure that the most crucial functions of a program work, but not bothering with finer details.
** Verify individual hardware or software units
- Integration (Integ)
** Verify inter-unit and external interfaces
- Functional (Func)
** Verify small groups of units and their interface ability to perform specific system and process functions
- System (ST)
Verify the complete system meets Func and Non-func Objectives and Requirements
Functional ST includes: External Interoperability of all data and control elements
Non-functional ST includes: Useability, Reliability, Efficiency, Portability, Maintainability
- Performance (Perf)
Covers Load, Volume, Stress and Exception testing
Ensures that changes have not adversely affected the pre-existing system(s) or application(s)
- User/Acceptance (UAT)
Validates the complete and integrated system against acceptance criteria and customer expectations.
- NOTE: Acceptance criteria are arrived at by aid of the System Requirements Specification (SRS), the Request For Proposal (RFP) and/or the Integration Test Plan (ITP)
Verifies the complete system co-operates with business processes and workflow, to meet stakeholder expectations in a production-like environment.
- Production Verification (PVT)
A repeat of the Pilot testing but under full production and business conditions
Test Phases Explained
- Smoke/Sanity Testing: Performed by
developers before releasing the build to the testing team.
May also be performed by testers to decide whether to accept the build for further testing or not.