Testing Services
Testing process
- Test Strategy >>
- Test Planning & Test Case Design
- Test Methodology
- Test Automation
Test strategy provides the foundation of the testing effort for a project.
Test strategy should clearly define roles and responsibilities, test types and methods. It defines the types of  testing to be conducted and establishes how, by whom and to what level the testing will be undertaken.
Using our extensive experience in planning test strategies for both large and small projects, we can evaluate the risks of not testing and ensure that any test strategy defines the appropriate level and type of testing required
We will identify and report on problems within your key business systems using best testing techniques defined in our methodology and utilizing our defect tracking system.
Test Strategy
OemSoftsales’s Testing Strategy & Planning process help you evaluate, build, and implement an effective QA and testing methodology that streamlines methods and uses available resources more efficiently.
The testing strategy is detailed as a comprehensive document that establishes the strategic direction of our work for you. Typically 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
We identify the features, components, sub-components, and items to be tested and the range of tests to be carried out. We identify available automation but also estimate required and possible automation. We catalog the tools used by the customer, potentially useful off-the-shelf tools, and internal OemSoftsales’s tools that may be used for the project.
We identify which features/components will be tested manually, which will be tested via automation, and what kind of automation tool is required (script-based, dedicated tool, etc)
The testing strategy is defined in collaboration with the customer. This  involves figuring out the order for scheduling so that test planning, test case design, test automation and test execution take into account key dependencies.