1 / 17

TESTING

TESTING. What is this symbol?. PURPOSE OF TESTING. There are three things you want to know about the system providing data:- Does work under normal conditions? Does it work at the extreme limits of operation? Is it capable of warning that bad data is being created?.

lydia-olsen
Download Presentation

TESTING

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. TESTING

  2. What is this symbol?

  3. PURPOSE OF TESTING • There are three things you want to know about the system providing data:- • Does work under normal conditions? • Does it work at the extreme limits of operation? • Is it capable of warning that bad data is being created?

  4. FOUR TESTING REQUIREMENTS • Data entry system testing (validation / input masks • Navigational and user interface testing (buttons and switch board) • Functional testing (Queries) • End user testing (Bonus)

  5. Importance of test plans A good test plan will have the following features: • To ensure all aspects of the data are covered, including normal, extreme and erroneous values • To document the data used - if anything goes wrong with the system later on, the original data tested can be rechecked. • To list the actions taken • To enable all tests to be reproduced • To list expected results • To be able to tie expected results to actual results

  6. CREATE YOUR TEST PLAN • Begin the create your test plan on Word • Advisable to use A3 landscape • Make sure your screen shots are clear • Be systematic and ordered

  7. TESTING PART 2Testing the navigation user interface • Test that the buttons work • Test that the navigation works • Test that data can be inputted • Test that Marcos work • Test switchboard You are not required top test every single button or example

  8. TESTING PART 3 Functional testing • The identification of functions that the software is expected to perform • The creation of input data based on the function's design / performance criteria • The determination of output based on the function's specifications • The execution of the test case • The comparison of actual and expected outputs

  9. Query that calculates total cost of the customers meal and the money made from the customer, returns values to a Form

  10. TEST PART 4: End user testing • Get the user to test it • Record their feedback and comments • Testing the software in use • Testing the data in real situations This could be an observation

  11. End user testing

  12. WHAT YOU NEED TO CREATE A TEST PLAN FOR AND WHAT TO TEST • All data entry (valid, invalid and extreme) • All Queries • All Forms (inc buttons) • All Reports • The switchboard • Macros • The user interface / design • Passwords • Functional testing: Compare and test database against performance criteria • End user testing • Everything...........

More Related