Your SlideShare is downloading. ×
Reporting On The Testing Process
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Reporting On The Testing Process

860
views

Published on

Published in: Technology, Education

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
860
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
24
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

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

×