It is very common to have a many tests that look alike. In most cases these test will have duplicate content perhaps to setup the environment for the test. This duplication can very very painful when the environment changes. The change to the enviroment will have to be made in all the tests that share the duplicated content. This can very tedious and time consuming work. Fortunately it can be avoided.

Using the Include widget is the key. Let's assume that our tests follow the standard BOC pattern and they look like this:

Included page: SampleSetupForTest (edit)

This is the Build step of our sample test.

It is common among multiple tests so it is saved in a separate page that can be included by test pages.

A table that sets up for a test

Included page: SampleOperateForTest (edit)

This is the Opertation step of our sample test.

It is common among multiple tests so it is saved in a separate page that can be included by test pages.

A table the performs an operation that needs checking

And now we'll perform the Check step.

A table that checks something

Keyboard Shortcuts ?

  • General

  • t Test page or suite
  • e Edit page
  • v View page (after test)
  • a Add new page

  • Go To

  • g u User Guide
  • g q Quick Reference Guide
  • g f Full Reference Guide
  • g c Recent Changes

  • Edit Mode

  • CTRL+s Save page
  • ESC Cancel edit

  • Tools

  • p Properties
  • w Where used?
  • AK+v Versions
  • AK+h Page History
  • / Focus on search bar
  • s Open search page
Close