Versions Compared

Old Version 16

changes.mady.by.user Frank Quern

Saved on

compared with

New Version 17

changes.mady.by.user Frank Quern

Saved on

Key

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

...

  • Adequate for the project
  • Validation by BPO should be tested before cutover weekend (some testers where not the normal executers or the transactions being tested)
  • Remote cutover testers should test connections to system before cutover weekend

Testing

 The Goal of testing is to find issues as soon as possible to avoid introducing defects into production.

  • Unit Testing
    • Definition of unit testing can be found on the QA wiki as well as this projects wiki
    • Keep the 5 day unit test window - new functionality has been introduced; the time for testing/resolving issues is needed
    • We used an Access db to store a catalog of the transactions we tested by whom and compared to last year
      • concept was good and has value
      • provided visibility to who was testing what as well as the status
      • the execution was rushed (the db was not really "production" ready)
      • the tool was a little klugy 
      • better solution should be explored (within SAP, within SM)
    • Should consider storing unit test cases in QC to promote a single consistant cataloging approach
    • A lot of discussion around what should be unit tested, how it should be tested and how it should be documented
      • QA will follow up on this effort
  • SIT/UAT Testing
    • QC - central repository for catalog of test cases
      • Worked well as a catalog for test cases 
      • Great for monitoring execution status
      • Saved preparation time of test "lab" for BAs (cases already in QC and available for use)
    • Test cases for the most part were not ready for QC formatting
      • Cases are/were designed for printing
      • A focused effort updating the cases to be QC formated would be beneficial to the process (requires resources)
    • Automation
      •  

Transports

  •  Transport management processes executed by the transport coordinator need to be documented.
  • Transport freeze
    • IS&T has this processed well defined and understood
    • Could explore another environment to allow development efforts during the freeze (assuming resources are available to do the work during the freeze)
  • Critical transport process
    • A consistent approach should be defined for all similar projects (there have been minor differences from project to project)

...

  • Communication
    • The Plan itself - well documented, easy to follow, clear as to who was doing what and when.
    • emails- Subscribe to email list of core team during the project/during cutover (watcher list could be added)** phone
    • status phone - was used throughout the weekend by IS&T staff
    • conference line - use WebEx to allow more participants on the call
    • validation steps
  • Execution
    • For the most part ran smoothly - went live slightly ahead of schedule
    • Cutover plan contained necessary details for successful execution
  • Other
    • Communication of Sunday attendance should be communicated earlier in the project to allow staff more time to plan ahead