Uploaded image for project: 'Request For Comments'
  1. Request For Comments
  2. RFC-742

JIRA Issue Type linked to Test Manager

    XMLWordPrintable

Details

    • RFC
    • Status: Implemented
    • Resolution: Done
    • DM, T&S
    • None

    Description

      We have had a request from SysEng and T&S to turn on Test Manager on the DM (now really software) JIRA project. Test Manager is the JIRA add-on that the verification teams use to create test plans and test cases The purpose for this change is that it would allow tickets to be linked to Test Run failures and vice versa.

      Do not be alarmed: We can configure this so it is not visible on existing issue types.

      I can create a new issue type, Fail, for Test Manager to be activated for. Since this won't affect existing uses at all, that's not what the RFC is about. The question here is whether some DM users would actually be interested in this functionality, in which case I suggest we repurpose the existing issue type Bug rather than go through all the work of adding a new issue type. Bug does not appear to be a heavily used issue type currently.

      If we did that, the effect on someone wanting to file a Bug without being interested in the Test Manager part would be that they would have an extra panel in their ticket that would be blank. Screenshot attached.

      If you care about whether we can re-use Bug (simplest option) versus creating a new Issue Type, comment below. Significant strength of feeling against using Bug nixes it.

      Attachments

        Issue Links

          Activity

            rowen Russell Owen added a comment - - edited

            I am strongly in favor of adding this section to Bug type tickets, because I think it would be less disruptive than trying to remember the difference between Fail and Bug. Also it seems innocuous to have an extra section that we can ignore.

            Do we have a use case for tying non-Bug tickets to tests? For example what if we want to allocate time to run a series of tests? I gently suggest expanding this RFC to include Story ("I am going to run some tests") and Milestone ("when these tests pass we have reached this milestone") as well. I don't see any point to Epic.

            rowen Russell Owen added a comment - - edited I am strongly in favor of adding this section to Bug type tickets, because I think it would be less disruptive than trying to remember the difference between Fail and Bug. Also it seems innocuous to have an extra section that we can ignore. Do we have a use case for tying non-Bug tickets to tests? For example what if we want to allocate time to run a series of tests? I gently suggest expanding this RFC to include Story ("I am going to run some tests") and Milestone ("when these tests pass we have reached this milestone") as well. I don't see any point to Epic.
            ktl Kian-Tat Lim added a comment -

            I can think of some kinds of test failures that may not be bugs per se (e.g. expected failures due to features not being ready yet or explainable failures due to external conditions), but I'm not sure that they occur in real life.

            This is the only means of accomplishing this linking (i.e. other Jira link mechanisms won't work), because of the nature of test runs?

            I hate to take up more room in an already-busy Jira screen, but the balance of not creating a new issue type does seem to suggest that this is the best way to go.

            ktl Kian-Tat Lim added a comment - I can think of some kinds of test failures that may not be bugs per se (e.g. expected failures due to features not being ready yet or explainable failures due to external conditions), but I'm not sure that they occur in real life. This is the only means of accomplishing this linking (i.e. other Jira link mechanisms won't work), because of the nature of test runs? I hate to take up more room in an already-busy Jira screen, but the balance of not creating a new issue type does seem to suggest that this is the best way to go.

            To answer KT's questions:

            I can think of some kinds of test failures that may not be bugs per se (e.g. expected failures due to features not being ready yet or explainable failures due to external conditions), but I'm not sure that they occur in real life.

            I think in such a situation one would not file a linked worked ticket (aroberts can confirm). I don't believe it is automatic, but I have not tried it myself.

            This is the only means of accomplishing this linking (i.e. other Jira link mechanisms won't work), because of the nature of test runs?

            Yes. Apparently the Test Manager thingimajobs are not native JIRA issue types so they cannot be linked in the usual way.

            frossie Frossie Economou added a comment - To answer KT's questions: I can think of some kinds of test failures that may not be bugs per se (e.g. expected failures due to features not being ready yet or explainable failures due to external conditions), but I'm not sure that they occur in real life. I think in such a situation one would not file a linked worked ticket ( aroberts can confirm). I don't believe it is automatic, but I have not tried it myself. This is the only means of accomplishing this linking (i.e. other Jira link mechanisms won't work), because of the nature of test runs? Yes. Apparently the Test Manager thingimajobs are not native JIRA issue types so they cannot be linked in the usual way.

            To answer Russel's questions:

            Do we have a use case for tying non-Bug tickets to tests? For example what if we want to allocate time to run a series of tests? I gently suggest expanding this RFC to include Story ("I am going to run some tests") and Milestone ("when these tests pass we have reached this milestone") as well. I don't see any point to Epic.

            I think there is nothing here that prevents us from opening stories related to verification work, and one can link the work to the overall test plan (eg https://jira.lsstcorp.org/browse/LVV-10) - the only thing that is being requested here is to link a DM ticket to a specific step failure if so desired, for which I think Bug is semantically appropriate, besides convenient.

            frossie Frossie Economou added a comment - To answer Russel's questions: Do we have a use case for tying non-Bug tickets to tests? For example what if we want to allocate time to run a series of tests? I gently suggest expanding this RFC to include Story ("I am going to run some tests") and Milestone ("when these tests pass we have reached this milestone") as well. I don't see any point to Epic. I think there is nothing here that prevents us from opening stories related to verification work, and one can link the work to the overall test plan (eg https://jira.lsstcorp.org/browse/LVV-10 ) - the only thing that is being requested here is to link a DM ticket to a specific step failure if so desired, for which I think Bug is semantically appropriate, besides convenient.
            frossie Frossie Economou added a comment - - edited

            This was nicely uncontroversial - aroberts you can turn on TestManager for Issue type Bug in the DM project. Can you please let me know when you have done so? (or link to the work ticket if you prefer)

            frossie Frossie Economou added a comment - - edited This was nicely uncontroversial - aroberts you can turn on TestManager for Issue type Bug in the DM project. Can you please let me know when you have done so? (or link to the work ticket if you prefer)

            frossie Test Manager has been turned on for Bug tickets only. Everything has been hidden that can be and only the test case executions that are linked to a bug ticket will show up in the traceability section. The permissions to create any of the Test Manager objects are set to the "Testers" role which is not being used on the DM project, so nobody can create any Test Cases, etc.

            aroberts Austin Roberts added a comment - frossie Test Manager has been turned on for Bug tickets only. Everything has been hidden that can be and only the test case executions that are linked to a bug ticket will show up in the traceability section. The permissions to create any of the Test Manager objects are set to the "Testers" role which is not being used on the DM project, so nobody can create any Test Cases, etc.

            People

              frossie Frossie Economou
              frossie Frossie Economou
              Andy Clements, Austin Roberts, Frossie Economou, Kian-Tat Lim, Krzysztof Findeisen, Russell Owen
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:
                Planned End:

                Jenkins

                  No builds found.