About using testRigor
Last updated
Last updated
especially useful if you re working with narrow monitors in a portrait mode
Therefore, keep on deleting tabs that are left behind.
It indicates that there are Test Cases in the Test Suite are failing.
However, when you are running a single Test Case it shows a yellow indicator "In progress".
After running one single Test Case successfully the panel may still show the red "Failed" indicator.
Therefore
for checking whether the Test Suite has failing Test Cases"
look at the indicator on the left panel
for checking whether a single re-run" Test Case has failed or passed:
look at the indicator of the latest "Run" of a Test Case
after each action testRigor will wait as per Settings > Speed optimizations
if a Test Case fails because the UI didn't refresh quickly enough
then you can specify an extra waiting time
Do this to select the first Recent Account in the Account lookup field:
navigate to "Tab/App" using App Launcher
Captured Data keeps a log of "Variables generated on test executions".
When the value is very long, then it's a bit hard to see the end part of the value.
You can try widening the window across several screens.
I don't know in which order the log is presented:
it's not in alphabetical order
it's not in chronological order
Yes, it would be useful to see more information, like timestamp, Test Case, prior value, ...
Hard stop
Move up the block that you are working on
when it's done then cut and paste it to the correct location in the test case
Test Suite can specify a "Parent Test Suite".
Test Cases, Test Data and/or Reusable Rules can be inherited from the "Parent Test Suite".
Only one level hierarchy is allowed:
a test suite that has specified a "Parent Test Suite" cannot be a Parent of another Test Suite
Child Test Suite
can Run and Re-run Parent Test Cases
"Runs" can be observed in test suite where they are "Run"
Test Case in Child Test Suite
can use Reusable Rules of the Parent Test Suite
Reusable Rule of the Parent Test Suite
can be opened form the Test Case of the Child Test Case (ctrl+click)
Observed once. Re-run was OK.