Reporting On The Testing Process


Published on

Published in: Technology, Education
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Reporting On The Testing Process

  1. 1. Testing & Evaluating Software Solutions Reporting on the Testing Process
  2. 2. Syllabus <ul><li>Documentation of the test data and output produced. </li></ul><ul><ul><li>Use of CASE Tools </li></ul></ul><ul><li>Communication with those for whom the solution has been developed, including: </li></ul><ul><ul><li>Test results </li></ul></ul><ul><ul><li>Comparison with original design specifications. </li></ul></ul>
  3. 3. Why do we need to report? <ul><li>Testing is a vital part of software development, but unless it is reported accurately there is no way to gain a full understanding of the solution. </li></ul><ul><li>Problems need to be highlighted and acted upon regularly. </li></ul>
  4. 4. Documentation of the Testing Process <ul><li>Test Requirements (What needs to be tested) </li></ul><ul><li>Reflect on the objectives and design specifications. </li></ul><ul><li>What tests need to be undertaken, why? </li></ul><ul><li>All aspects of the entire system should be tested. </li></ul>
  5. 5. Documentation of the Testing Process <ul><li>Test Plan (How do we implement the tests?) </li></ul><ul><li>Include a schedule and time line of events. </li></ul><ul><li>Include and document the use of CASE tools. </li></ul>
  6. 6. Documentation of the Testing Process <ul><li>Test Data & Expected Results (What are the inputs and expected outputs) </li></ul><ul><li>All test data and expected results should be documented. </li></ul><ul><li>If modifications are made then the entire testing process needs to be run again. </li></ul><ul><li>Identify why the entire testing process needs </li></ul><ul><li>to run again for minor module modifications </li></ul>
  7. 7. Documentation of the Testing Process <ul><li>Test Results (Do actual results meet expected results?) </li></ul><ul><li>All results should be kept for justification and evaluation. </li></ul><ul><li>They can also be used to confirm that modifications have been made. </li></ul>
  8. 8. Documentation of the Testing Process <ul><li>Recommendations (What needs to be done now?) </li></ul><ul><li>Bugs have been identified so therefore strategies must to employed concerning how to fix them. </li></ul><ul><li>All bugs should be accessed concerning severity. </li></ul><ul><li>1. Dialog box not centred </li></ul><ul><li>2. Logic Error when getting results </li></ul>
  9. 9. Communication of Process <ul><li>Communication is an important practice in the overall completion of software development, but also in regards to testing. </li></ul><ul><li>This communication must take place between: </li></ul><ul><ul><ul><li>Developers and client </li></ul></ul></ul><ul><ul><ul><li>Outsourced testers and developers </li></ul></ul></ul>
  10. 10. Developers and Client <ul><li>This communication should address objectives that have not been met. </li></ul><ul><li>Communication should also be non-technical. </li></ul><ul><li>The provision of graphical methods to display data will help clients develop a mental image i.e. Onsite practical demonstration and checklists </li></ul>
  11. 11. Communication with Developers <ul><li>Sometimes the testing process is outsourced to testing departments or forms. </li></ul><ul><li>All findings and evaluations should be clearly presented and supported with specific facts. </li></ul><ul><li>A climate of cooperation should be evident between all parties in this process. </li></ul>
  12. 12. Use of CASE Tools <ul><li>It is appropriate and often necessary for developers to use specialised CASE tools as they provide structured assistance, sometimes automated processes and development of test data. </li></ul>
  13. 13. Example 1 – Test data generator <ul><li>Name – Win Runner </li></ul><ul><li>Function – It is a functional testing tool. It </li></ul><ul><li>creates a variety of test data items to be entered </li></ul><ul><li>into a system and analyses expected with actual </li></ul><ul><li>output. </li></ul>
  14. 14. Example 2 – Volume Tester <ul><li>Name – LoadRunner </li></ul><ul><li>Function – Is a simulation program that tests </li></ul><ul><li>simultaneous use. Through the creation of </li></ul><ul><li>virtual users a simulation is created. All results </li></ul><ul><li>are evaluated for developers. </li></ul>