Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: Science Pipelines, Verification
-
Story Points:4
-
Epic Link:
-
Team:DM Science
Description
Create the test plan and report for the 2019 Fall science pipelines release acceptance test campaign.
Attachments
Issue Links
Activity
If a test case is changed, after it has been included in a test cycle, the update WILL NOT be propagated automatically to the test cycle itself.
You have to go to the test cycle, tell the test player to get the updated version of the test case.
This looks great. I really like having the "Example Code" block shown in the steps; right now it's often butler initialization but I can see us using it a lot more as we refine some of more involved steps. The particular tests I was confused about are all cleaned up now. It's ready to go from my perspective.
Colin Slater
added a comment - This looks great. I really like having the "Example Code" block shown in the steps; right now it's often butler initialization but I can see us using it a lot more as we refine some of more involved steps. The particular tests I was confused about are all cleaned up now. It's ready to go from my perspective. OK - I set LVV-P65 to Approved.
The document has been uploaded in Docushare and merged to master.
Yep - I'm gonna work through the Test Cases today.
I just learned that the reason the old one shows up in the document is that a Test Cycle includes the version at the time it was added. So if you update a Test Case, you have to update the Test Cycle as well.