- The VENDOR has to ensure that testing begins as early as development and is carried hand in hand with development.
- The VENDOR has to involve the test engineer early in the development process.
- The VENDOR should ensure that once testing begins, the developers must create the test data, enter it into the system and write the test plan.
- The VENDOR must use QUICK FPA for estimation of testing effort along with development effort calculation.
- The VENDOR should develop a test plan by using estimated number of test cases for test management system.
- The VENDOR
- THE VENDOR should know and be certain about the timing at which the test plans will be created during the development process.
- THE VENDOR must share the test plan (test cases) with the CLIENT regularly for review.
- Following test strategy should be crafted by the VENDOR and get approved by the CLIENT –
- Who is responsible for quality testing?
- At what point in the development will the build be tested?
- When the test data needs to created and who is responsible for creating it?
- What are the testing types and what testing tools are to be used?
- Who will be responsible for unit testing?
- When can be the product be open to automated testing during the product life cycle?
- The VENDOR’s testing team must perform functional and validation testing to check for consistency with variable data inputs e.g. (checking validation of form with different data sets) – The form must run smoothly for all variations in data inputs.
- The VENDOR must do testing for format, special characters and all types of scenarios.
- The VENDOR must define the tools that would be used for automated, performance and integration testing to the CLIENT beforehand.
- In case of any scope change, the VENDOR must update the test plan and inform the CLIENT of the same.
- The VENDOR must always take the Quality testing estimate into consideration while developing/changing the Product Road Map.
- The VENDOR must use a checklist /testing document to keep a check/trace & prevent a new bug creation every time an old bug gets reported and rectified by the CLIENT.