Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Draft ....

.... basead on August 29, 2006 code migration meeting:

Attendees:
Sandra Steward
Pat Kava
Emily Stumpf
Jon Gorrono
Scott Amerson
Thomas Amsler


As a trial, we will adopt the following test documentation process:

  • Programmers create a JIRA Main Test Task (MTT) that describes the
    whole test and is the anchor for all Sub Test Tasks.
  • A confluence page may be created to
    1. provide related or more detailed explanation of the test assumptions, etc
    2. provide an organizing structure to a test suite and/or
    3. to provide I/O matrices and other test tools to aid the testers.
  • Programmers create Sub Test Tasks (STT) or Test Tasks (LTT) that are
    linked to the Main Test Task
    • Each of these STTs/LTTs describes a testable unit
    • Once QA has tested a STT/LTT, QA will post test results for each of
      these unites and indicate if the test passed or failed as comments to the JIRA MTT
  • Once the test has completed, programmers will review all test
    results and create JIRA bug tickets as necessary
    • If a JIRA bug ticket is created, it is directly linked to the
      corresponding STT/LTT
  • If there are test results that indicate failure and the programmers
    haven't created a JIRA bug ticket for it, for some reason, this test
    result will be discussed among Code Migration Meeting attendees and a
    decision will be made if there is a need to create a JIRA troube/bug
    ticket at that time.
  • No labels