Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-16076

Create test plan for LDM-503-09a

    Details

    • Type: Story
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: DM
    • Labels:

      Description

      LDM-503-09a “Pipelines Release Fall 2018”

      Pending release procedure ... though the test we run should not depend on that,.

        Attachments

          Issue Links

            Activity

            Hide
            swinbank John Swinbank added a comment -

            Mail to Gabriele Comoretto from me, 2018-11-16:

            Hi Gabriele,

            I would like to generate a new DMTR (test plan & report) to cover
            milestone LDM-503-09a.

            I believe that I have entered all of the necessary information into
            Jira. In particular, this test document should cover:

            Test plan LVV-P15;
            Test cycle LVV-C18;
            Test cases LVV-362 & LVV-363.

            Note that I have literally just written all of the above. They are not
            currently collected in a test specification document. From reading our
            documentation, I don't understand if it is possible to execute these
            tests before they are part of a test specification. Could you please
            advise?

            If it is not possible, and given that we'll need this test plan ready to
            go soon (the milestone is due at the end of the month), could you please
            advise how best to have these incorporated into a test specification?

            I would also value your feedback on whether the plan/cycle/cases
            described above are well formed. This is my first attempt at using the
            Jira based system, and — while I hope I did a good job! — I'm sure there
            are things I misunderstood.

            I also have a question about the test management in Jira. What's the
            meaning of the “not covered” status? For example, DMS-REQ-308-V-01 is
            listed as “not covered”, but it is apparently covered by six test cases,
            two of which have been approved... so what does “not covered” mean?!

            Thank you very much for your help, and have a good weekend!

            John

            Show
            swinbank John Swinbank added a comment - Mail to Gabriele Comoretto from me, 2018-11-16: Hi Gabriele, I would like to generate a new DMTR (test plan & report) to cover milestone LDM-503-09a. I believe that I have entered all of the necessary information into Jira. In particular, this test document should cover: Test plan LVV-P15; Test cycle LVV-C18; Test cases LVV-362 & LVV-363 . Note that I have literally just written all of the above. They are not currently collected in a test specification document. From reading our documentation, I don't understand if it is possible to execute these tests before they are part of a test specification. Could you please advise? If it is not possible, and given that we'll need this test plan ready to go soon (the milestone is due at the end of the month), could you please advise how best to have these incorporated into a test specification? I would also value your feedback on whether the plan/cycle/cases described above are well formed. This is my first attempt at using the Jira based system, and — while I hope I did a good job! — I'm sure there are things I misunderstood. I also have a question about the test management in Jira. What's the meaning of the “not covered” status? For example, DMS-REQ-308-V-01 is listed as “not covered”, but it is apparently covered by six test cases, two of which have been approved... so what does “not covered” mean?! Thank you very much for your help, and have a good weekend! John
            Hide
            swinbank John Swinbank added a comment -

            Wil O'Mullane, Leanne Guy — these tests are now defined in Jira as:

            Test plan: LVV-P15;
            Test cycle: LVV-C18;
            Test cases: LVV-362 & LVV-363.

            The test report has been issued as DMTR-111 and is now available at https://dmtr-111.lsst.io/.

            Please confirm that you are happy that this plan addresses verification of milestone LDM-503-09a.

            Show
            swinbank John Swinbank added a comment - Wil O'Mullane , Leanne Guy — these tests are now defined in Jira as: Test plan: LVV-P15; Test cycle: LVV-C18; Test cases: LVV-362 & LVV-363 . The test report has been issued as DMTR-111 and is now available at https://dmtr-111.lsst.io/ . Please confirm that you are happy that this plan addresses verification of milestone LDM-503-09a.
            Hide
            womullan Wil O'Mullane added a comment -

            It may be worth mentioning e.g. in the scope, that there are other metrics and tests run on a release this is not the only test but is the final one to declare the milestone complete.

             

            But ok for me – Leanne Guy please set to review complete when you are done.

            Show
            womullan Wil O'Mullane added a comment - It may be worth mentioning e.g. in the scope, that there are other metrics and tests run on a release this is not the only test but is the final one to declare the milestone complete.   But ok for me – Leanne Guy please set to review complete when you are done.
            Hide
            lguy Leanne Guy added a comment -

            I have submitted a PR with typos / grammar corrections. Some of the corrections as the same as for DM-16072. Otherwise OK for me

            Show
            lguy Leanne Guy added a comment - I have submitted a PR with typos / grammar corrections. Some of the corrections as the same as for DM-16072 . Otherwise OK for me
            Hide
            swinbank John Swinbank added a comment - - edited

            I have made the following changes in Jira:

            • Added a sentence to the test plan clarifying the scope of this work;
            • Made some changes to the text in Jira following suggestions on the GitHub PR (some of the suggestions there were stylistic, rather than matters of correctness; I have not made changes I disagreed with, and I trust that's ok!).

            A number of the comments on the PR refer to typos in Docsteady, which have been or are being addressed elsewhere.

            Gabriele Comoretto, when Docsteady is ready to go, please generate a new version of the DMTR. At that point, I think we can close this ticket.

            Meanwhile, given there's no disagreement with the test plan as defined in Jira, I think we're ready to execute these tests as soon as the v17 release is out.

            Show
            swinbank John Swinbank added a comment - - edited I have made the following changes in Jira: Added a sentence to the test plan clarifying the scope of this work; Made some changes to the text in Jira following suggestions on the GitHub PR (some of the suggestions there were stylistic, rather than matters of correctness; I have not made changes I disagreed with, and I trust that's ok!). A number of the comments on the PR refer to typos in Docsteady, which have been or are being addressed elsewhere. Gabriele Comoretto , when Docsteady is ready to go, please generate a new version of the DMTR. At that point, I think we can close this ticket. Meanwhile, given there's no disagreement with the test plan as defined in Jira, I think we're ready to execute these tests as soon as the v17 release is out.
            Hide
            gcomoretto Gabriele Comoretto added a comment -

            New version of the document has been generated and is available at following link:

             

            https://dmtr-111.lsst.io/v/DM-16076

             

            Note: I used the previous created ticket branch, and I rebased on the latest master. In any case, the entire document has been regenerated from Jira using the new template.

            John Swinbank, if you are OK with it, the PR can be opened.

            Show
            gcomoretto Gabriele Comoretto added a comment - New version of the document has been generated and is available at following link:   https://dmtr-111.lsst.io/v/DM-16076   Note: I used the previous created ticket branch, and I rebased on the latest master. In any case, the entire document has been regenerated from Jira using the new template. John Swinbank , if you are OK with it, the PR can be opened.
            Hide
            swinbank John Swinbank added a comment -

            Gabriele Comoretto — same comments here as on DM-16072. Specifically:

            I'm getting confused about which fixes are available in which versions of Docsteady, and which DMTRs have which issues resolved. Given that, and given that I don't want to keep correcting the same errors in multiple places, I think the right thing to do here is wait until DM-16768 is resolved then re-generate and re-review DMTR-112. Do you agree?

            As you know, I'm also confused about what has to be done to formally lift the test plan out of “draft” status, and I'd appreciate your guidance on that.
            When the above have been completed, I think we can close this ticket (unless further issues arise).

            Show
            swinbank John Swinbank added a comment - Gabriele Comoretto — same comments here as on DM-16072 . Specifically: I'm getting confused about which fixes are available in which versions of Docsteady, and which DMTRs have which issues resolved. Given that, and given that I don't want to keep correcting the same errors in multiple places, I think the right thing to do here is wait until DM-16768 is resolved then re-generate and re-review DMTR-112. Do you agree? As you know, I'm also confused about what has to be done to formally lift the test plan out of “draft” status, and I'd appreciate your guidance on that. When the above have been completed, I think we can close this ticket (unless further issues arise).
            Hide
            gcomoretto Gabriele Comoretto added a comment -

            The changes documented in DM-16768 are already implemented, and DMTR-111 has been regenerated accordingly.

            There is the procedural aspect still to sort out, the changes in LVV-P15 if not already done and the folder organization in Jira to map tp the product tree.

            Show
            gcomoretto Gabriele Comoretto added a comment - The changes documented in  DM-16768  are already implemented, and DMTR-111 has been regenerated accordingly. There is the procedural aspect still to sort out, the changes in LVV-P15 if not already done and the folder organization in Jira to map tp the product tree.
            Hide
            swinbank John Swinbank added a comment -

            Thank you Gabriele Comoretto — the document as currently sitting on the ticket branch looks good to me. I will merge it and close this ticket.

            Show
            swinbank John Swinbank added a comment - Thank you Gabriele Comoretto — the document as currently sitting on the ticket branch looks good to me. I will merge it and close this ticket.

              People

              • Assignee:
                swinbank John Swinbank
                Reporter:
                womullan Wil O'Mullane
                Reviewers:
                Leanne Guy, Wil O'Mullane
                Watchers:
                Gabriele Comoretto, John Swinbank, Leanne Guy, Wil O'Mullane
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Due:
                  Created:
                  Updated:
                  Resolved:

                  Summary Panel