Wednesday, 1 July 2009

Purpose and content of a Test Plan

In contrast to the Test Strategy, the Test Plan document defines the actual testing scope for a particular product or a particular phase within a product development. In other words, your company might decide that the software will be released in 3 stages and each stage will require complete testing before being released to the public. It could even be that, during each stage of release, there maybe requirement to create a test plan for each phase of the testing, e.g. Integration Testing, System Testing and User Acceptance Testing.

In other words, a Test Plan could exist either for a single release of software or single stage of testing phase. Either way, the content should remain pretty much the same for both cases.

A test plan states what features to be tested, what features not to be tested and why, at what level they will be tested, what order they are to be tested in.

The purpose of a test plan is to provide a plan of verification that the software produced meets the functional or design requirements or specification. 


The following is a typical content of a Test Plan (formalised as IEEE 829-2008 standard):
  • Test plan identifier
  • Introduction
  • Test items
  • Features to be tested
  • Features not to be tested
  • Approach
  • Item pass/fail criteria
  • Suspension criteria and resumption requirements
  • Test deliverables
  • Testing tasks
  • Environmental needs
  • Responsibilities
  • Staffing and training needs
  • Schedule
  • Risks and contingencies
  • Approvals

Monday, 29 June 2009

Purpose and content of a Test Strategy

I've often being asked by interviewers the same questions again and again and it it this: "What is the purpose of a Test Strategy document and what is the content?" and every time I was asked this question, I must have given a different answer in each case. But I thought I'd write down the definitive answer to that question so I won't have to remember it again.

A Test Strategy is either a company level document which defines the standard testing approach to be taken across all projects, or a project level document which defines the standard testing approach to be taken across all stages of testing. 


The contents of test strategy can consist of the following:
  1. Scope and Objective
  2. Budget control
  3. Testing approach
  4. Test deliverables: A list of deliverables to be produced during a software project, e.g. test plan, test cases, test data, text execution results, defect reports and test completion report.
  5. Roles and responsibilities: Identifying the type of test roles needed and each of their responsibilities, e.g. test manager, senior test analyst, tester, automated test engineer, etc.
  6. Communication and status reporting: The type of reports to be generated  and their frequency
  7. Automation tools: (if needed)
  8. Testing Measurements: How success and failures of the testing will be judged and the kind of measurements to be used to access project success
  9. Change configuration management
  10. Training plan


Monday, 23 March 2009

FTSE Trend Forecasting Using Neural Nets

This is a preliminary work I did for a trading house in London in 1994, where they wanted to use Neural Networks to forecast the direction of the FTSE from London Stock Exchange. The paper is presented here for historical reference.