Page History

...

1. Create a Test Plan in Jira 
   • A Jira issue should already be available to trace this activity
   • The Jira Test Plan has to be created in the corresponding folder, that maps to a product in the product tree. The folder name will be the used as "product name" in the DMTR.
   • The Test Plan name shall correspond to the test milestone name (if defined): <Milestone ID> <Milestone Name>
2. Complete the the Test Plan with all relevant information required before the test activity can start (see DM Test Approach)
   • The fields "Overall Assessment" and "Recommended Improvements" need to be empty. Will be filled after the test activity has been completed.
3. Create a Test Cycle and trace it to the above Test Plan
   • Multiple Test Cycles can be create for the same Test Plan
   • Each Test Cycle corresponds to a specific hardware / software / configuration set-up.
4. Complete the the Test Cycle(s) with all relevant information required before the test activity can start (see DM Test Approach or ask the configuration engineer in case of doubts)
   • In the traceability tab, add the test cases you want to execute in the Test Cycle
   • Note that a test case can be added only once to a Test Cycle
5. The Test Plan and Report is generated from Jira using docsteady (by the configuration engineer, to be automated in Jenkins)
   • Procedure to generate the DMTR:
     • Create the Docushare entry for the test plan and report (you get a DMTR-XXX)
     • Create the repository in github.com/lsst-dm (tex README and .gitignore)
     • Create a new branch tickets/DM-xyz where DM-xyz is the Jira issue that tracks the activity to create the test plan
     • Copy from an old DMTR (for example DMTR-161) the following files:
       • Makefile (to be updated with the new document handler)

       • appendix.tex

       • history_and_info.tex (to be updated with the proper information: history, curator, handler)

     • Generate the document using the following command:
       • docsteady generate-tpr --username [YourJiraUser] --password [YourJiraPassword] LVV-PYYY DMTR-XXX.tex
     • Ensure that the pdf is produced correctly using make command (contact BVAN or GCM if not)
     • Add and push to GitHub the DMTR-XXX plus the 3 files above
     • Ask JSick to activate dmtr-xxx.lsst.io publication page
     • Regenerate the document each time changes have been done in Jira.
     The update is done in a ticket branch of the document repository
   • The publication page lsst.io will make available the drafted changes (ask JSick to configure it, if not already done).
   • Note that all section of the DMTR are is generated automatically. Sections in the appendix can be added and maintained in the repository , if needed.
6. When all information requested before the test can start are are available:
   • Set Jira issue status to "In Review" (the Jira issue assignee).  Remember to indicate who are the reviewers (Leanne and Wil, or who requested the test)
   • Create a PR on the ticket branch (the Jira issue assignee) with the same reviewers listed in the Jira issue 
   • Comments are made in the PR by the reviewers and changes are applied in Jira test Plan and Test Cycle(s) bu the Jira assignee
7. When all comments are satisfied and the PR is approved (Jira issue set to Reviewed):
   • The test plan status will be set to "Approved" (by the Jira assignee)
   • The document regenerated from Jira one last time into the branch (by the configuration engineer, to be automated in Jenkins)
   • The branch is merged into master ( by the Jira assignee)
   • The test is ready to start.
8. Execute the test using the test player available in each Test Cycle
   • This activity is usually documented in a new Jira issue
9. When the test activities are completed:
   
   • Complete the fields "Overall Assessment" and "Recommended Improvements" in the Test Plan (the Jira issue assignee)
   • The Test Cycle(s) status is set to "Done" (the Jira issue assignee)
   • Update the DMTR in a (new) ticket branch using docsteady (the configuration engineer, to be automated in Jenkins)
   • Adjust content in Jira in order that the DMTR generated with docstead docsteady is OK (the Jira assignee and the configuration engineer)
   • Set the Jira issue status to "In Review" (the Jira assignee) assigning the appropriate reviewers
   • Create a PR on the ticket branch (the configuration engineer) with the same reviewers of the Jira issue.
   • Comments are made in the PR by the reviewers and changes are applied in Jira test Plan and Test Cycle(s) by the Jira assignee
10. When all comments are satisfied, the  DMTR is ready to be finalized:
    • The PR is approved and the Jira issue status is set to "ReviewdReviewed" (by the reviewers)
    • The Test Plan status is set to "Completed" in Jira (by the Jira assignee)
    • The DMTR content is regenerated one last time from Jira (by the configuration engineer, to be automated in Jenkins)
    • The ticket branch is merged into master (by the Jira assignee)
11. The DMTR is approved by the person who requested the test activity.