Review
Testing
Results
Prepared by Kaloyan Titov
, INDEX
Contents of this presentation:
1. Evaluation of test results, using both graphical and written methods.
2. Comparison of passed, failed and skipped tests and suggest improvements to the test plan, focusing on
the process of testing and how it can be improved in the next round of testing.
3. Improving the software product and the quality assurance processes.
4. Providing justification about each test, why they have failed etc.
5. Reasons why skipped tests were not provided.
6. The successful presentation needs to be easy to read by a third party, it must be logically structured and it
should use technical language and software testing terminology accurately.
, EVALUATION OF TEST RESULTS
Evaluation of test results:
Every software product, must have a testing plan and testing results. Those results help us
understand how our product is performing and what needs to be improved on, to meet the client
requirements. Product testing can help us find any issues that are ongoing with our application and
adjust them accordingly so they do not affect the usability or any other performance factors that
might cause the application to crash or to be exposed to a security breach. According to the tests
that I have conducted in this project, my program seems to be quite robust, despite having a couple
of issues that I have addressed and talked about potential fixes. The tests that I conducted show
that the program is functioning accordingly to the client brief, meeting all of the necessary criteria
and all information is careful provided. The test results show that my program is a complete
example of what is needed from the brief. The test results also show that my program needs a few
adjustments in order to make it fully robust, which is why we using testing results, to determine
whether the program is suitable for the release. My program is ready for a realise, but there has
been a couple of issues that have been identified, which do not affect the usability or functionality,
therefore we can go ahead with the release.
Testing
Results
Prepared by Kaloyan Titov
, INDEX
Contents of this presentation:
1. Evaluation of test results, using both graphical and written methods.
2. Comparison of passed, failed and skipped tests and suggest improvements to the test plan, focusing on
the process of testing and how it can be improved in the next round of testing.
3. Improving the software product and the quality assurance processes.
4. Providing justification about each test, why they have failed etc.
5. Reasons why skipped tests were not provided.
6. The successful presentation needs to be easy to read by a third party, it must be logically structured and it
should use technical language and software testing terminology accurately.
, EVALUATION OF TEST RESULTS
Evaluation of test results:
Every software product, must have a testing plan and testing results. Those results help us
understand how our product is performing and what needs to be improved on, to meet the client
requirements. Product testing can help us find any issues that are ongoing with our application and
adjust them accordingly so they do not affect the usability or any other performance factors that
might cause the application to crash or to be exposed to a security breach. According to the tests
that I have conducted in this project, my program seems to be quite robust, despite having a couple
of issues that I have addressed and talked about potential fixes. The tests that I conducted show
that the program is functioning accordingly to the client brief, meeting all of the necessary criteria
and all information is careful provided. The test results show that my program is a complete
example of what is needed from the brief. The test results also show that my program needs a few
adjustments in order to make it fully robust, which is why we using testing results, to determine
whether the program is suitable for the release. My program is ready for a realise, but there has
been a couple of issues that have been identified, which do not affect the usability or functionality,
therefore we can go ahead with the release.
