Software Testing

• What is software testing and why do it?
• Why test early and often?
• Why use a structured, well-planned approach to testing?
• Human factors - peers, managers, customers

Test Strategies

• Strategic planning - defining the overall approach
• Writing test process guidelines/a master test plan
• Defining test activities
• Identifying and managing testing risks
• Budgeting, scheduling and estimating

Test Documentation

• Why write test documents? (objectives)
• Using the IV&V test document template
• Tailoring standards to suit your needs

Reviews

• Reviewing document (using checklists)
• Reviewing tests and test execution
• Reviewing progress

Requirements

• The role of testers in requirements reviews
• The "Reminder" Functional Specification
• Identifying good and bad (and ugly) requirements
• Requirements tracing

Unit Testing

• Verifying that the code is implemented as designed
• Documenting unit tests
• The hand-over from Developer to Tester
  Requirements-based Testing
• Managing the software risks

Functional Testing

• Verifying that the requirements are met
• Planning tests - a "Reminder" exercise
• Designing tests using a variety of test types & methods
• Writing test cases & procedures for the "Reminder" application

System Testing

• Validating that the system is fit for purpose
• System testing re-used and COTS software

Test Tools

• Classes of tools
• When are tools a good idea and a bad idea?
• A sensible approach to automation

Running Tests

• Controlling the test environment
• Running tests and debugging procedures
• Problem reporting

Test Metrics - The feedback loop

• What should I collect? What can it tell me?
• How should I measure / graph the data?
• Analyzing test results - when to stop testing

Regression Testing

• What is regression testing?
• What do you retest?

Final Acceptance

• Making sure you are ready for system release
• Final acceptance - audits and tests
• Writing test reports