CONTROLLED DATA
Leidos Proprietary - US Citizens ONLY
The information contained herein is proprietary to Leidos, Inc. It may not be used, reproduced, disclosed, or exported without the written approval of Leidos.

Use this guide when creating test plans, test sets, tests and other tasks in JIRA/XRAY to validate development activities and ultimately releases.

Step-by-step guide

High Level Understanding:
  1. Review Design Plans, JIRA development tasks and Requirements to determine what testing is needed to validate success
  2. Create or link a Test or Test Set to verify the capability to be developed
    1. Test → Single set of steps, can be used for unit testing or end to end testing
    2. Test Set → Set of tests that cover happy path and fringe cases for an end to end test case
  3. Once the JIRA task is closed, complete test executions for each test associated
  4. Test Plan → A collection of tests and/or test sets associated with a release.
    1. Executions against a test plan will provide 'release readiness' reporting

Assignments and Status in XRAY

  1. Tests 
    1. Created status = New and assignment is to have a tester populate with test steps
    2. Status = ready to test once the test steps are created to address the associated task/issue/requirement
    3. Start Test 'button' utilized once development is completed making the status=in progress
    4. Tests will never be passed/failed. They will become our 'library'. Each execution of the test will be associated as needed to report on test readiness
  2. Test Sets
    1. Created to track a set of tests such as all tests to validate a new orderable service (DMUC) or to associate multiple tests for 'fringe' cases. Another example would be smoke tests (1 per component)
    2. The description should clearly list the desired tests to be included
  3. Test Plans
    1. Associate multiple tests and/or test sets together to perform executions and track for release readiness.
    2. Regression testing will be a test plan with a base of needed tests such as 'happy path' service and portal tests along with smoke tests.
  4. Test Executions
    1. 1 execution per environment
    2. Failed steps will have clear comments regarding the failure. For now, test lead will disposition failures by attaching/creating bugs or flagging it for retest.

 





The information contained herein is proprietary to Leidos, Inc. It may not be used, reproduced, disclosed, or exported without the written approval of Leidos.
CONTROLLED DATA