Given below is the generic service delivery model followed by Web Spiders Practice.
Web Spiders selects the ideal delivery model based on each customer’s specific business case.
A very high-level workflow of the interaction process between the customer and Web Spiders is illustrated below:
- The client sends the introductory mail mentioning the outline of the QA job that he/she is looking for.
- The QA Manager goes through it and responds with a set of queries.
- The client responds and asks for the test plan and sample test cases.
- The QA Manager prepares the test plan and mails it along with a few sample test cases.
- The test plan is reviewed and finalized by both the parties.
- The QA Manager discusses the project with the team members and the test cases are prepared.
- Test cases are executed for a particular version of the product, reviewed and mailed to the client.
- The bugs are approved by the client and debugged by his/her development team.
- Depending on the project requirements, the client releases the next version of the project for QA and the test plan and test cases are updated, accordingly.
- The same process is repeated.
Once all the bugs have been reported, and the project is re-tested and de-bugged, the QA process concludes.
