Software features and functions are tested during the test phase, generally in a separate test environment. There are various types of tests (e.g., unit, integration, system, stress), but all test cases are run to verify the correctness and completeness of the software. Successful test execution validates the efficiency and effectiveness of the requirements and design.

The testing phase actually overlaps with requirements, design and development phases. It's critical that the test plan, test scenarios and test cases reflect all the business, end-user, customer, and architecture and design requirements - as defined within the Requirements traceability matrix (RTM). There are many types of testing that may have to be included in the overall test plan.

For example, there is at least one self-proclaimed expert who state there are at least 100 different types of software test that can be conducted. Over the course of your project management careers you may be exposed any number of these testing requirements. However, the most basic testing requirements include the following: (In typical order of the testing)

The Testing Phase of the SDLC includes the scope of work necessary to analyze and document testing requirements to ensure the solution will implement desired capabilities and perform in accordance with all customer, business, and end-user requirements. End-users will test and validate conformance of the user interfaces, screens, data fields, data flows, and reports that enable the business processes and/ or user functionality. Technical testers will ensure the underlying hardware, software, network, database, work flow, and security components conform to architectural, design and performance requirements.

Independent Software Quality Assurance (QA) tests will confirm the development team has followed the organization's quality processes and procedures, and that the solution meets established quality metrics. Another independent group will conduct IV&V Tests to verify the solution meets requirements, and validates the system meets the customer's needs. Defects and bugs that are uncovered during testing will be documented and prioritized. All critical defects will be fixed prior to going into production.