Managing the Test Environment Managing Changes Before you make changes to the

Managing the test environment managing changes before

This preview shows page 39 - 41 out of 96 pages.

the problem recurring. Managing the Test Environment Managing Changes Before you make changes to the Acceptance Test environment, make sure they are planned, authorised, controlled, recorded, and communicated to Test participants. Otherwise: even minor changes may impact the validity of tests already completed; and participants can become confused if the status and versions of the Test environment are uncertain. Keeping Track of Testing Progress Establish an Acceptance Test Log to record all significant events occurring within the Acceptance Test environment. The Log should be readily accessible and should be used (mainly by the Acceptance Test Manager and System Administrator) to log changes to: The system software; System documentation; System parameters, code tables, and reference data; Baseline Test Data; Migrated Test Data; External systems and/or data; Database software, configuration and scripts; and/or Network, server, and workstation software, and configuration. The information you could log includes: The date and time of an event; The name of the person executing an event; Details of the event; The signature of the authorising person; and Any comments about the event and its outcome. Managing Test Data Initialising Test Data Initialisation usually involves loading or entering: The necessary system codes and system parameters; Template – Acceptance Test Log
Image of page 39
The Acceptance Testing Kit – Part 2 27 Backing up at strategic points will enable you to more easily return to an historical data position in the testing process, with less time and effort. Once you’ve prepared your test data, make a copy should the data become corrupted in the future. It’s useful for when further system changes are made and another round of testing is required. Either manual or automated Test Scripts and Test Data required for the Tests; and Migrated data (usually used where large volumes of data are required, and often from a separate database). When testing an upgrade to an existing system, the Test database will normally be populated with data extracted or copied from the existing live database and there may be little or no need to add additional data. When testing a new system, the Test database will probably be empty and need setting up with an initial Test dataset. Some data may be loaded automatically from spreadsheets, text files, or other databases using database scripts. However, data may need to entered directly using the system’s standard on- line functions. Backing up the Acceptance Test Database Regularly backing up the Acceptance Test database allows recovery of the database if the need arises to re-test, or to eliminate corrupt, spurious, or unnecessary data. Usually, backups (and any necessary restores) need to be authorised by either the Acceptance Test Manager or the System Administrator, and should be recorded in the Acceptance Test Log.
Image of page 40
Image of page 41

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