TOSCA TRICENTIS AS1 ACTUAL SCRIPT
WITH 100 PERCENT CORRECT ANSWERS
◉ How the ActionMode Verify is used?
Answer: "Verify" is used to check on the value to validate against
expected results in the TestCase. For example, it might be
important to verify that a particular shipping method you chose
for a product you had ordered adds the correct amount to your
total.
◉ How the ActionMode WaitOn is used?
Answer: You select "WaitOn" when you want to perform a
dynamic wait for a control property to reach a specified state.
Alternatively, you use "WaitOn" to wait for an entered value before
continuing the execution. Once the condition is satisfied, Tosca
reacts and continues the automation workflow.
This is Best Practice over inserting a static wait, as this decreases
the overall execution time.
◉ How the ActionMode Buffer is used?
Answer: Tosca uses the ActionMode Buffer to save any type of
value generated during the execution of the TestCase. It can either
be a static or a dynamic value. This value will be temporarily
saved in Tosca and can be used later on in the same TestCase.
, ◉ How the ActionMode Constraint is used?
Answer: The ActionMode Constraint can used on a specific list
item to identify the respective list item. A combination of selected
values can be used to identify the list item.
◉ How to run a Test Case?
Answer: Right-click on the Test Case and select Run in
Scratchbook.
A section of the test case can be run by selecting objects and then
press F6 to run the selected objects.
Add and arrange objects in the ScratchBook and then run them.
◉ What is the ScratchBook?
Answer: The ScratchBook is a Tosca built-in capability that allows
you to perform trial runs of your TestSteps and TestCases.
Such trial runs create only a temporary result. This temporary
result is not saved and will be overwritten once you'll run a new
TestCase or TestStep in the ScratchBook.
After execution, the results will appear in the ScratchBook. If a
TestStep fails, a red X appears next to the step with log info,
explaining what the error was. When everything runs correctly,
the steps are marked with a green check mark.
WITH 100 PERCENT CORRECT ANSWERS
◉ How the ActionMode Verify is used?
Answer: "Verify" is used to check on the value to validate against
expected results in the TestCase. For example, it might be
important to verify that a particular shipping method you chose
for a product you had ordered adds the correct amount to your
total.
◉ How the ActionMode WaitOn is used?
Answer: You select "WaitOn" when you want to perform a
dynamic wait for a control property to reach a specified state.
Alternatively, you use "WaitOn" to wait for an entered value before
continuing the execution. Once the condition is satisfied, Tosca
reacts and continues the automation workflow.
This is Best Practice over inserting a static wait, as this decreases
the overall execution time.
◉ How the ActionMode Buffer is used?
Answer: Tosca uses the ActionMode Buffer to save any type of
value generated during the execution of the TestCase. It can either
be a static or a dynamic value. This value will be temporarily
saved in Tosca and can be used later on in the same TestCase.
, ◉ How the ActionMode Constraint is used?
Answer: The ActionMode Constraint can used on a specific list
item to identify the respective list item. A combination of selected
values can be used to identify the list item.
◉ How to run a Test Case?
Answer: Right-click on the Test Case and select Run in
Scratchbook.
A section of the test case can be run by selecting objects and then
press F6 to run the selected objects.
Add and arrange objects in the ScratchBook and then run them.
◉ What is the ScratchBook?
Answer: The ScratchBook is a Tosca built-in capability that allows
you to perform trial runs of your TestSteps and TestCases.
Such trial runs create only a temporary result. This temporary
result is not saved and will be overwritten once you'll run a new
TestCase or TestStep in the ScratchBook.
After execution, the results will appear in the ScratchBook. If a
TestStep fails, a red X appears next to the step with log info,
explaining what the error was. When everything runs correctly,
the steps are marked with a green check mark.
