Tag: testing

Understanding what managers value about testing.

write objective and factual incident reports and review findings

Identifying potential customer work-arounds for bugs

Promoting better quality software whenever possible.

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

User acceptance testing

System testing

Integration testing

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

System tests are often performed by independent teams.

Faults found during system tests can be very expensive to fix.

End-users should be involved in system tests.

Functional testing is used more than structural testing.

time runs out.

the required level of confidence has been achieved.

no more faults are found.

the users won’t find any serious faults.

It includes the verification of designs.

It states that modules are tested against user requirements.

It specifies the test techniques to be used.

It only models the testing phase.

Features to be tested

Incident reports

Risks

Schedule

possible communications bottlenecks in a program.

the rate of change of data values as a program executes.

the intrinsic complexity of the code.

the use of data on paths through the code.

An inspection is lead by the author, whilst a walkthrough is lead by a trained moderator.

An inspection has a trained leader, whilst a walkthrough has no leader.

A walkthrough is lead by the author, whilst an inspection is lead by a trained moderator.

Authors are not present during inspections, whilst they are during walkthroughs.