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

Write test report for LDM-503-3

    Details

    • Type: Story
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: None
    • Story Points:
      4
    • Sprint:
      Alert Production F17 - 11, AP S18-1, AP S18-2
    • Team:
      Alert Production

      Description

      Write up the results of the test documented in LDM-533.

        Attachments

          Activity

          Hide
          ebellm Eric Bellm added a comment -

          And the test report?

          Show
          ebellm Eric Bellm added a comment - And the test report?
          Hide
          swinbank John Swinbank added a comment -

          This looks basically fine. I've added some comments to the PR, but they boil down to two issues I think:

          • For everything that's broken (ie, that should've worked but didn't), we should have a JIRA ticket linked in the test report. These will be the Software Problem Reports assessed by the CCB. If we can convince the CCB that they are "noncritical" (e.g. because they are within reasonable tolerances) then we can claim the test as having been passed.
          • Most of our failures are due to things which haven't been implemented, and in some cases things for which the requirements haven't even yet been properly established. Rather than writing these up as failures, my suggestion would be to document them as "deviations from test procedure". That means we are properly reporting on the success (or otherwise) of code which actually exists now, but maintaining those parts of the test cases so that they will be executed when we come to re-run the tests with a more mature stack in future.
          Show
          swinbank John Swinbank added a comment - This looks basically fine. I've added some comments to the PR, but they boil down to two issues I think: For everything that's broken (ie, that should've worked but didn't), we should have a JIRA ticket linked in the test report. These will be the Software Problem Reports assessed by the CCB. If we can convince the CCB that they are "noncritical" (e.g. because they are within reasonable tolerances) then we can claim the test as having been passed. Most of our failures are due to things which haven't been implemented, and in some cases things for which the requirements haven't even yet been properly established. Rather than writing these up as failures, my suggestion would be to document them as "deviations from test procedure". That means we are properly reporting on the success (or otherwise) of code which actually exists now, but maintaining those parts of the test cases so that they will be executed when we come to re-run the tests with a more mature stack in future.

            People

            • Assignee:
              ebellm Eric Bellm
              Reporter:
              ebellm Eric Bellm
              Reviewers:
              John Swinbank
              Watchers:
              Eric Bellm, John Swinbank
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Summary Panel