...
- Put each step in a separate line (a separate row in Qmetry)
- Provide a high-level summary of what needs to be done in each step
- Do not specify OS-specific commands
...
- Add a summary to the test of fewer than 50 characters
- Provide a unique test name.
- We recommend providing the issue ID in the name of the test suite as a reference ### we don's use these any more, so this should probably go away
- Provide a high-level summary of what needs to be done in each step. Avoid providing commands as sometimes they are system-specific or might change in future. ### Is this different from what we say in "Instructions", above?
- Only specify server/sched and MoM options or log messages if they are public/stable or contractual. Avoid specifying any command that is private/unstable ### I think we're not using these terms any more
- Refer to guides for any upgrade or installation steps. DO NOT add any upgrade or installation steps in the test. Also DO NOT add reference to a section in PBS guides as it may change in future.Similarly DO NOT provide any failover or peer server, etc .. setup in the test configuration. ### what if we're testing failover??
Make sure that each step is unambiguous.
...