Record and Categorise Problems To keep track of Testing and Test problems the

Record and categorise problems to keep track of

This preview shows page 42 - 44 out of 96 pages.

Record and Categorise Problems To keep track of Testing and Test problems, the Acceptance Test Manager needs to monitor and report on Acceptance Testing progress and the status of outstanding problems. Each recorded problem will reference the relevant Test Case, Test Script, and business requirement (or requirements as detailed in the Contract). Problems will be graded by priority (severity and impact) and categorised by type.
Image of page 42
The Acceptance Testing Kit – Part 2 30 Problems that can only be resolved by re-specifying business requirements (compared to those in the Contract) should still be recorded but categorised so as to be clearly identifiable as a possible future change request or Contract variation. Attempt Resolving Problems With the Supplier Management of any contractual issues arising from Acceptance Testing is best left to the Acceptance Test Manager and Project Manager who will try to resolve the problems with the Service Provider Project Manager. The outcome of any discussions needs to be recorded against individual problems as they appear in the Problem Review Register. The Acceptance Test Manager and the Service Provider Project Manager will endeavour to agree on the definition of the problem and a possible solution. If agreement can’t be reached as to the cause of or responsibility for any problem, refer the matter to the Project Sponsor or Project Steering Committee. Fixing Problems and Retesting Change Control When Acceptance Testing occurs, it is in a defined and agreed environment, against an agreed Plan and timetable, with agreed Test data, against agreed Acceptance Criteria and with a specific delivered version of the system and documentation. Any changes to these items should be managed and assessed by the Project Team, the change impact defined, measured and costed, and due consideration given to the change before it is approved and applied. Where changes to the Test environment, the system, or the Test data are made, they may impact the integrity of Testing already completed. System Upgrades and Retesting The Acceptance Test Manager will need to manage and authorise any upgrades or changes to the Acceptance Test environment required to resolve Testing problems. All changes to the system and Acceptance Test environment should be logged. The system supplier should provide details of changes and the problems that have been resolved with each new Release. Where applicable, regression testing may need to be undertaken to confirm that new problems have not been inadvertently created by changes that resolve other issues. The number of new releases should be as few as possible and should be stipulated in the Contract. Ideally, there should be only one subsequent release of the system.
Image of page 43
Image of page 44

You've reached the end of your free preview.

Want to read all 96 pages?

  • Fall '18
  • acceptance testing, Acceptance Test Manager

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture