Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

What Is a Test Case?

A test case is a written description of the steps to be taken in order to validate a behavior.  The test case should contain all of the information and instructions the tester needs.

Components of a Test Case

...

  • Add a summary to the test. Give a unique test ID and a test summary of fewer than 50 characters  ### is ID part of summary?  Or is this 2 steps?
  • We recommend providing the issue ID in the name of the test suite as a reference
  • 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.
  • 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
  • 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.


Make sure that each step is unambiguous.

Notes on Test Execution

  • Refer the related documentation. For example, if testing on a special branch then refer the branch specific documentation and EDD along with generic PBS guides,
  • Sometime new features might not be documented in time. If not able to find information in PBS guides then refer the respective EDD. Also one might have to follow up with the project team who has delivered the feature on the status of documentation and previous testing.
  • Link PBS documentation and product bugs to the tests if they are failing either due to missing documentation or product behavior.

...