Test Planning
At QA Labs, Test Planning is the foundation of successful software testing, but we know how challenging it is for project teams to produce comprehensive test cases when the schedule is tight.
We help by putting project requirements through an analysis process that ensures the highest priorities get tested first in the time available.
Test Strategy
The QA Labs Test Strategy is the cornerstone of our methodology. Simply put, it is a comprehensive document that establishes the strategic direction of our work for you. It includes:
- Quality Requirements and Goals
- Scope of Testing
- Tasks to be performed and how they will be undertaken
- Resources and Tools
- Schedules and Milestones
- Project and Testing Risks
- Dependencies of the Testing Effort
- Providing a well-defined testing roadmap
Test Analysis
Our Test Analysis pinpoints precisely what tests will be performed. It provides feedback that the requirements have been covered for each test type. By reviewing the requirements, QA Labs’ Test Analysis raises critical issues early in the project lifecycle to prevent errors from reaching the code.
In the case of incomplete or absent requirements, QA Labs can rapidly “reverse engineer” those artifacts for Test Planning purposes. This makes enumeration and confirmation of the expected behaviors easy, typically with little impact on the overall testing schedule.
Documenting the Tests
Different kinds of software may require radically different testing techniques, timeframes and cost considerations. QA Labs testing documentation includes:
- Build Verification and Acceptance
- Functionality
- Error Handling
- Compatibility
- Scalability
- User Interface (UI)
- Usability
The above take the form of individual Test Cases and/or task-oriented Test Scenarios or Test Scripts. Other types of testing are included as described in the Test Strategy.
Read more about Test Strategies and Test Planning on our Resources page.
Test Planning Process
Our Test Planning process can include:
- Project Familiarization
-
- Identifying and reviewing the existing project documentation (use cases and/or requirements)
- Functionality walk-through (demo, mock-ups, user training)
- Requirements Review (for completeness, consistency, correctness, unambiguity, testability, etc.)
- Defining the overall scope of testing for the project
-
- Defining the Test Strategy and scope of each type of testing to be performed
- Defining the Test Environment(s)
- Determining which tools and testing utilities will be needed
- Determining applicability of manual vs. automated testing
- Identifying and evaluating skills/resources available
- Configuring the Test Environment(s)
-
- Defining the test environment requirements
- Performing installation and configuration of test tool(s)
- Test Planning and Test Case Design
-
- Test Analysis of the Requirements to enumerate the tests to be performed for each requirement for each type of testing.
- Expanding the Test Analysis into Test Cases and/or Test Scenarios and prioritizing the same.
