Versions Compared

Old Version 3

changes.mady.by.user Unknown User (wbastos)

Saved on

compared with

New Version 4

changes.mady.by.user Unknown User (bartd)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Review each test catalog and mark the test cases required to be executed for Support Pack testing.
  2. Add new cases that are not in the catalog.
  3. Update existing test cases if needed with current up to date steps.  This should include adding steps to the catalog.
  4. Create a list or identify Unit test cases (1 week) (Note: This should be only core functionality testing, ie..open programs, run core transactions to ensure there are no catastrophic failures).
  5. Identify what test cases from the catalog will be tested in System Integration Testing (2 weeks). 
  6. Work with the business units to identify the UAT test cases from the catalog.
  7. Encourage teams to move test steps from separate test script documents into test catalog spreadsheet. Benefits: One document used during testing to record results; Facilitate future migration to Quality Center.

Test Phases

Unit Test

System Integration Test

User Acceptance Test

  1. Core team: Technical & Functional responsibility
  2. Discrete tests, not end-to-end scenarios
  3. Scripts optional
  4. List of what was tested required
  1. Core team: Functional leads responsibility, but may optionally involve business
  2. Scripts required
  3. Discrete tests or end-to-end scenarios, but end-to-end scenarios must cover discrete tests of critical functions
  1. Business owner responsibility
  2. Scripts required
  3. End-to-end scenarios
  4. Don't duplicate tests performed in System Integration Test phase