Configuration Management

Question 1

Poor configuration management

Answer 1

Can’t find latest source code
Can’t replicate previously released code
fixed bugs reappear
Wrong code tested
Tested features disappear

Question 2

Types of software risk

Answer 2

Project risk - resource constraints, external interfaces, supplier relationships
Process risk - variance in planning and estimation, failure to track progress
Product risk - lack of requirements, stability , complexity

Question 3

Why track incidents

Answer 3

Provide developers and other parties with feedback about problem to enable identification, isolation and correction if necessary
To provide test leaders a means of tracking quality of system
Provide input to test process improvement initiatives

Question 4

Incident reporting

Answer 4

Describe what’s wrong
Document test script and script step identifiers
Attach any outputs
Reports, comments, workflow