Quality Management Testing Types:

• Functional testing via automated scripts
• Functional testing via manual scripts
• Automated/Manual performance testing
• Manual performance testing by end users (User Acceptance Test)
• Automated load testing

A test plan approach incorporates the following principles:

• Planning and scheduling
• Test the most critical and highest risk features first.
• Development of test scripts based on business requirements and functional specifications.
• Ensure all gaps in testing have been identified.
• Develop repeatable test scripts to facilitate defect before implementation and identify possible best practices.
• Determine validation and verification techniques for each test cycle/phase to quickly detect error or omissions.
• Test with appropriate subject matter experts (SME) and end-user involvement.
• For each project functional testing will vary depending on scope and complexity.

Test Phases

Goals and Benefits

• To ensure that a thorough review of the projects functionality and requirements have been achieved.
• Validate targeted business processes, rules, parameters, security and customizations.
• Identify errors or omissions that may hinder a successful release of the service.
• Aid in gap analysis efforts by collaborating with the project team.
• Testing will assist to ensure a stable production environment with remediation of any critical error finds.
• Testing methodology can render decrease in implementation time as SMEs to understand will have a clear understanding of requirements as they develop test scripts, create process documents/maps with testing in mind and work with users.
• Testing will decrease risk, as processes and load will be tested as close to a production environment as possible.

Functional Testing Process Overview