Uploaded image for project: 'Gazelle Test Management'
  1. Gazelle Test Management
  2. GZL-4382

mysterious disappearances in NA2017 testing session


    • Type: Bug
    • Status: Closed
    • Priority: High
    • Resolution: Done
    • Affects Version/s: Gazelle TM 5.4.1
    • Fix Version/s: Gazelle TM 5.4.6
    • Component/s: None
    • Labels:
    • Severity:
      Blocker - Show stopper, feature completely blocked, crashes or data corruption
    • Sprint:
      2017 - S1
    • Account:
      Maintenance 2016 (MAINTENANCE2016)


      (1) Last week, I noticed that some systems that I believed I had approved for Supportive testing had Thorough testing for “Testing type”. I reset Supportive testing for 3 or 4 systems. Then, I checked to see if there were others, and I found 71 AIPOs spread across 20 different test systems with ‘Wanted test type’ of Supportive’ and ‘Registered test type’ of Thorough. This seemed odd to me since Steve & I believe we finished that work…. However, sometimes my memory is bad, so I dismissed it.

      (2) ***Then***, yesterday Steve was working on assigning IP addresses. He noticed that a small number of systems had no default configs, even though he believed that he had finished that work.

      (3) Three patients that were part of preload demographics (Patient Generation and Sharing) are now gone. See yellow highlighted patients in the attachment. These were in the NA2016 demographics but they no longer exist. I suppose someone could have deleted them manually, but why? and all of the other ones are there. I will create a separate issue to have them re-created since tests rely on those patients, and I am not going to redo that work.

      Now we have three mysterious disappearances, so it’s harder for me to dismiss this as incomplete work.

      Do you have any ideas about what might have happened? Are there other areas (eg pre-Connectathon test results) that may have been affected?? What risk does this pose for NA Connectathon week?




            • Assignee:
              lfelhofer Lynn Felhofer
            • Votes:
              0 Vote for this issue
              3 Start watching this issue


              • Created:

                Time Tracking

                Original Estimate - 4 hours
                Time Spent - 1 hour, 30 minutes Remaining Estimate - 2 hours, 30 minutes
                2h 30m
                Time Spent - 1 hour, 30 minutes Remaining Estimate - 2 hours, 30 minutes
                1h 30m

                  Potential Duplicates