Initial draft. #1
Conversation
index.rst
Outdated
| @@ -4,9 +4,93 @@ Night Planning Tool | |||
|
|
|||
| .. abstract:: | |||
|
|
|||
| This technote describes the design of an integrated night planning tool. This is a tools that allows our team to collect a group of Jira tickets that describes a set of tests, allows us to organize these into a coherent list of tests to execute, that can later be loaded and executed at the summit. | |||
| This technote describes the design of an integrated night planning tool. | |||
| This is a tools that allows our team to collect a group of Jira tickets describing a set of tests/observations, allows us to organize these into a coherent list that can later be loaded and executed at the summit. | |||
There was a problem hiding this comment.
Typo
"This is a tool that allows ..."
There was a problem hiding this comment.
... "tests/observations, allows us to organize" ...
Consider splitting the sentence here.
index.rst
Outdated
|
|
||
| - SITCOM are used to capture high level tests/verification activities. | ||
| They are usually connected to one or more requirement or some other commissioning activity. | ||
| For example, SITCOM-1099 was created to capture the tests required to validate the operation of the system with the TMA dynamic settings going from 5% all the way to 100% of its requirements. |
There was a problem hiding this comment.
Weak suggestion - convert SITCOM-1099 into a link.
| - BLOCK tickets are used to design, plan, execute and track activities at the summit. | ||
| Usually a BLOCK ticket will be linked to a SITCOM ticket. | ||
|
|
||
| Up to now, planning activities at the summit have revolved around collecting the BLOCK tickets that will be executed at night and sorting them out in a table with some information about priority and order of execution. |
There was a problem hiding this comment.
Maybe add a link to one of the night plans/logs for a practical example? Here is one for convenience:
https://confluence.lsstcorp.org/display/LSSTCOM/2024-04-23+Simonyi+Night+Log
|
|
||
| We will adopt Jira's Zephyr application to create test cases, test cycles and test plans to organize how tests will be executed and planned. | ||
|
|
||
| - BLOCK tickets will be used to describe what the block does, link it to a particular SITCOM ticket and will also aggregate the block configuration. |
There was a problem hiding this comment.
If we adopt Zephyr, I recommend that we limit BLOCK tickets for those who will have JSON files or scheduler configurations. I don't see why we need to create a BLOCK ticket and a test case if that does not favor automatization/scripting.
There was a problem hiding this comment.
I am not sure about this. For example, see the doc page that Erik is working on describing the BLOCK project workflow. I think there is some value to having a BLOCK ticket. However, this might be a good discussion to have with the rest of the team.
There was a problem hiding this comment.
Can we have a couple of examples here? I believe, the way this is now, it is too abstract for a discussion.
There was a problem hiding this comment.
I think Erik's document would be a better place for this information. I am going to link Erik's document here and will add an item in the FAQ to talk about this.
|
|
||
| - BLOCK tickets will be used to describe what the block does, link it to a particular SITCOM ticket and will also aggregate the block configuration. | ||
|
|
||
| - Test Cases will have a step by step description of how to execute a particular BLOCK. |
There was a problem hiding this comment.
Including instructions to setup/wrap-up.
|
|
||
| - Test Cycles will be used to plan a particular night. | ||
| They contain a list of Test Cases, ordered in the same way they should be executed. | ||
| The Environment field is used to separate the Test Cases that will be executed at different parts of the day; Daytime, Afternoon, Early Night, Late Night, etc. |
There was a problem hiding this comment.
The time periods are something that I would like to agree on and have it set in stone.
There was a problem hiding this comment.
agree... let's discuss that in the next meeting.
tribeiro
force-pushed
the
tickets/DM-44231
branch
from
83e0c66
to
2c71773
Compare
No description provided.