Tag: testing

Testing is not context dependent

Exhaustive testing is possible

Early testing is impossible

Absence-of-errors fallacy

Test Analysis and Design

Test Planning and Control

Test Implementation and Execution

Evaluating Exit Criteria and Reporting

Checking which planned deliverables have been delivered

Finalizing and archiving testware, the test environment and the test infrastructure for later reuse

Handing over the testware to the maintenance organization

Writing a test summary report for stakeholders

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.