Testing is the most important component of the project quality assurance and it is vital to define and implement a successful testing strategy in order to ensure a high quality product output.

Testing Quality assurance

The Test Plan is created to document in details the project testing strategy, the test components, the test estimations, and the test planning, resources and tools.

A “standard” project test strategy will target a clear set of test goals to be achieved, such as:

  • Provide (at least) 80% automated unit tests coverage
  • Perform all the appropriate types of product testing:
    • Unit testing
    • Functional testing
    • Non-Functional testing:
      • Performance
      • Security
      • User experience/UI
      • Platform
      • Integration
      • Localization
      • Globalization
      • Accessibility

The project test strategy will be defined based on the following rules and best practices:

  • Develop an optimal combination of automated test cases and manual test cases.
  • Discuss and approve the test cases design with the Product owner(s) and/or the client.
  • Plan for the testing effort in each Sprint and execute as planned – make testing part of the “Done” Sprint exit criteria.
  • Use a test environment which reproduces as close as possible the product “live” setup.
  • Involve customer (early in the project lifecycle) in the testing activities.