Exploratory testing can replace black box techniques when testing time is very limited

Test execution scheduling should give priority to experienced based testing

Specification based techniques can be used as a substitute for a poorly defined test
basis

Experienced based techniques are systematic and produce detailed test documentation

 Decision table testing

State transition testing

Statement testing

Boundary value analysis

Developer and independent testing will overlap and waste resources.

Communication is limited between independent testers and developers.

Independent testers are too slow and delay the project schedule.

Developers can lose a sense of responsibility for quality.

Use decision tables to generate the Boolean test conditions to be executed.

Identify the structure of the system or software at the component, integration or system
level.

Use the skill, intuition and experience of the tester to derive the test cases, using error
guessing and exploratory testing.

Establish traceability from test conditions back to the specifications and requirements.

1

2

3

4

Independence from the production process

A belief that programmers always make mistakes

Knowledge of the number of defects typically found in a program

Confidence that the next stage will find defects missed at this stage

Testing to see where the system does not function properly

Testing quality attributes of the system including performance and usability

Testing a system feature using only the software required for that action

Testing a system feature using only the software required for that function

Testing for functions that should not exist

Analysing the test basis

Assigning resources for the planned activities

Designing the test environments

Writing a test execution schedule