Softheme approach to testing web projects contains the following steps:
1. Analyze project business requirements and functional specifications that will be used as a reference and basis;
2. Get familiar with the application that is planned to be tested (if available);
3. Create Vision document that describes approach to testing, identifies project schedule, tools, deliverables, team profile;
4. Estimate Level of Efforts, come up with costs;
5. Approve Vision and LOE;
6. Identify testing approach:
- what functionality will be tested? what are the usability and accessibility requirements? what scenarios should be covered at the first place?
- how the test data will be generated?
- what additional constraints should be taken into account (e.g. order of the modules that will be delivered will impact on the testing schedule; critical areas; etc.)?
7. Create test strategy that:
- contains description of the features to be tested, test coverage;
- specifies approach to testing;
- provides pass/fail criteria;
- lists test deliverables;
- detalizes responsibilities, staffing, schedule, and environmental needs;
8. Create test plan, test scenarios and scripts, checklists, test cases;
9. Agree on a build schedule;
10. Test the application; report the results to Defects Tracking Tool following the established Reporting Procedure;
11. In course of testing all the information (including documents, reports, and test results) will be available for the client’s review on the secure project environment;
12. The approach chosen for testing will maximize test coverage and optimize the time required to create test scenarios and scripts and execute them.
See also: Softheme Software Testing Approach
How We Assist in Your Product’s Improvement
good