Test Execution and Testing: Say No to Narrow Thinking

Test Execution and Testing: Say No to Narrow Thinking
July 14 06:35 2016 Print This Article

People in a software testing company often think that testers just execute test cases and occasionally update or create them.

This wrong belief may negatively affect the work of a software tester, and hence it should be revised and disproved. Actually, the execution of tests may be considered as the least important part of software testing. Several much more substantial and demanding aspects are present in the testing process.

What Does the Testing Process Include?

  • Mental model of the product under test. Presence of such a model allows testers to deeply understand and estimate the testing scope, project outcome and possible risks.
  • Creation of effective tests. Using the already created mental model, testers decide what to test and how to test it. After that, they design and create the required tests based on obtained results.
  • Test execution itself. When tests are ready, manual testing or automated testing can be executed. If needed, execution of tests can be only partially automated. Test execution is the process of performing functional testing or other required testing types.
  • Results analysis. This activity helps to allocate the problem, figure out whether it really is a problem, evaluate its severity and discuss it with other project participants.
  • Reporting the results. Test reports should necessarily include the steps to reproduce a bug and other valuable information.

To manage not only the test execution, but the entire process of testing, project participants can use end-to-end test management tools.

Related Posts:

About Article Author

view more articles
Nataliia Vasylyna

View More Articles
  • Vivek Singh

    Nice share, According to me it is a continuous process. Whatever the points you have mention all these points can’t be end at single point. Before handover the project to the client, it requires to test from depth to higher coding level. Whenever changes are require at any phase of the project. It should need to retest whole process. Testing process can only complete at a single point i.e NO ERROR!.