TESTING

17
TESTING

description

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?. - PowerPoint PPT Presentation

Transcript of TESTING

Page 1: TESTING

TESTING

Page 2: TESTING

What is this symbol?

Page 3: TESTING

PURPOSE OF TESTING

• There are three things you want to know about the system providing data:-

1. Does work under normal conditions?

2. Does it work at the extreme limits of operation?

3. Is it capable of warning that bad data is being created?

Page 4: TESTING

FOUR TESTING REQUIREMENTS

1. Data entry system testing (validation / input masks

2. Navigational and user interface testing (buttons and switch board)

3. Functional testing (Queries)4. End user testing (Bonus)

Page 5: TESTING

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

Page 6: TESTING

Test Number

Description of test

Data / procedure

entered

Data Level Expected result

Actual result Outcome

1 Enter in customers name into customer

table

Jones Valid Data inputted

The validation

check works

Test Number

Description of test

Data / procedure

entered

VALID

INVALID

EXTREME

Expected

result

Actual result Outcome

1 Enter in customers

mobile number

07815654356 Data inputted

The validation check works

2 Enter in name instead of customers

mobile number

Barry Data rejected

error message

The validation check works

Page 7: TESTING

Test Number

Testing Description of test

Data / procedure

entered

Data Level Expected result

Actual result Outcome

1 Validation of age field,

13 - 19

Enter 100 into age

field

100 Extreme Error message

Use aksed to renter correct

data

Screen shot of result The errot message showed as expected

2 Validation of age field,

13 - 19

Enter twelve

into age field

twelve erroneous Error message

Use aksed to renter correct

data

Screen shot of result The errot message showed as expected

Page 8: TESTING

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

Page 9: TESTING

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

Page 10: TESTING

Test Number Description of test

Method Expected result

Actual result Outcome

1 Check that Close button on Customer form closes

the form and returns to

switch board 5

Click button Form will close switch board will

open

The validation

check works

Page 11: TESTING

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

Page 12: TESTING

Test Number

Description of test Method OutcomeUsers Comments

1 There will be three buttons leading to three other switchboards

observation

Page 13: TESTING

Test Number

Description of test

Method Expected result Result (screen shot)

Outcome

1 Run find total cost query, should find all cots up to current date and return in a form

Click Button 5 on switch board 2

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

Page 14: TESTING

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

Page 15: TESTING

Test Number

Description of test

Method End user comment Screen shot Outcome

End user testing

Page 16: TESTING
Page 17: TESTING

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...........