Item, Operation, Value, Comments

Item, Operation, Value, Documentation

Item, Operation, Property, Documentation

Number, Operation, Value, Documentation

F3

SHIFT+ALT+F3

CTRL+SHIFT+F3

F10

Call Action

Split Action

Reusable Action

None

GetData(Row,Col)

GetRowValue(Rowid,Colname)

GetCellData (Row,Col)

GetRowValue(Row,Col)

True

False

True

False

True

False

True

False

True

False

Each test stage has a different purpose

It is easier to manage testing in stages

We can run different tests in different environments

The more stages we have, the better the testing

Integration testing

Regression testing

System testing

User acceptance testing

The system shall be user friendly.

The safety-critical parts of the system shall contain 0 faults.

The response time shall be less than one second for the specified design load.

The system shall be built to be portable.

find as many faults as possible.

obtain good test coverage

test whatever is easiest to test.

test high risk areas

System tests are often performed by independent teams.

Functional testing is used more than structural testing.

Faults found during system tests can be very expensive to fix

End-users should be involved in system tests.

time runs out.

the required level of confidence has been achieved.

no more faults are found.

the users won’t find any serious faults.

syntax testing

equivalence partitioning

stress testing

modified condition/decision coverage

Boundary value analysis

Usability testing

Performance testing

Security testing

Statement testing

Path testing

Data flow testing

State transition testing

possible communications bottlenecks in a program.

the rate of change of data values as a program executes

the use of data on paths through the code

the intrinsic complexity of the code.

User requirements

Actual results

Program specification

System specification