Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space DTPDEVEL and version 5.4.1

...

  • flow.threshold: The flow works on a scoring system. A change in test result from one build to the next affects the score. By default, if the score exceeds 0, the test is considered unstable. If test status fluctuation is expected, you can change the threshold to a higher value so that tests are considered stable despite a moderate change in status over the set number of builds. 
  • flow.maxBuildCount: By default, TSR uses the 10 most recent builds as the sample size for determining test stability. You can change the maxBuildCount value to include more or fewer builds. Using more builds will affect system performance.
  • flow.algorithm: The built-in algorithm is used to calculate test stability by default, but you can specify custom in this field and program your own algorithm in the Calculate Stability (custom) function node.

 

To use the custom algorithm, you will also need to double-click the Switch Algorithm function node and specify the custom algorithm.

...

After deploying the artifact, the Test Stability - Donut and Test Stability - Statistics widgets will be available in the DTP under the Process Intelligence category.  Test See Adding Widgets for instructions on adding widgets to the dashboard.

...

TitleEnter a new title to replace the default title that appears on the dashboard.
FilterChoose Dashboard Settings to use the dashboard filter or choose a filter from the drop-down menu (see Creating and Managing Filters for more information about filters in DTP).
Last Run

The widget shows data for the last run based on test status. You can choose:

  • All to include all tests in the last run.
  • Passed to include only the tests that passed in the last run.
  • Failed to include only the tests that failed in the last run.
  • Incomplete to include on only the tests that did not complete in the last run.
  • No Data to include only the tests that did not report a status.

You can add multiple instances of the widget configured with different last run settings to create a more complete view of your test stability.

...