Tag: testing

the first testing that is performed.

pre-release testing by end user representatives at the developer’s site.

post-release testing by end user representatives at the developer’s site.

pre-release testing by end user representatives at their sites.

an error

a fault

a failure

a defect

testing that the components that comprise the system function together

testing that the system functions with other systems

testing the system performs functions within specified response times

testing the end to end functionality of the system as a whole

the use of a variable before it has been defined

memory leaks

unreachable (“dead”) code

array bound violations

ensuring that the system is acceptable to all users

testing the system with other systems

finding faults in the system

testing from a business perspective

re-testing looks for unexpected side-effects; regression testing ensures the original fault has been removed

re-testing is done after faults are fixed; regression testing is done earlier

re-testing is done by developers; regression testing is done by independent testers

re-testing ensures the original fault has been removed; regression testing looks for unexpected side-effects

management review

walkthrough

inspection

post project review

yes, because testing includes all non-constructive activities

no, because they apply to development documentation

yes, because both help detect faults and improve quality

no, because they are normally applied before testing

as the first approach to deriving test cases

by inexperienced testers

after more formal techniques have been applied

after the system has gone live

when the test completion criteria have been met

when all planned tests have been run

when no faults have been found by the tests run

when time for testing has run out