TOSCA TRICENTIS AS1 COMPREHENSIVE
TEST PAPER WITH SOLVED QUESTIONS
◉ Best Practices for Template verification.
Answer: Once you have linked the TestSheet and its Values to the
Template, it's important to check for errors.
When updating an existing Template is easy to make mistakes.
The Check Template function is very helpful in these cases.
◉ What to do when a Template has been updated with an updated
TestSheet?
Answer: Delete the old TemplateInstances folder from
the previous Template.
We are now ready to Instantiate.
This step is very important because, up until now, the changes and
new values haven't been transferred into the TestCasesInstances.
Only after Instantiation, we will have complete TestCases that
include the verification.
This can also be done by highlighting the Template and using the
keyboard shortcut CTRL+N, CTRL+I.
, ◉ Key Points for Modifying Templates.
Answer: 1. A verification Attribute has a value that Tosca uses to
verify against the SUT Output.
2. Check the Template for Reference before modifying it.
3. Use the Check Template function after modifying a Template.
◉ What are Conditions in Tosca?
Answer: Conditions instruct Tosca on when to use (or not to use)
certain TestSteps, TestFolders, or Values.
For example: A condition on a TestStep Folder will act as a rule for
when the content of the entire folder will be run.
A condition on a TestStepValue will just be applicable on that
specific Value.
◉ What are the Benefits of Conditions in Templates?
Answer: Conditions avoid Template repetition.
Using appropriately set Conditions means only one Template is
needed.
TEST PAPER WITH SOLVED QUESTIONS
◉ Best Practices for Template verification.
Answer: Once you have linked the TestSheet and its Values to the
Template, it's important to check for errors.
When updating an existing Template is easy to make mistakes.
The Check Template function is very helpful in these cases.
◉ What to do when a Template has been updated with an updated
TestSheet?
Answer: Delete the old TemplateInstances folder from
the previous Template.
We are now ready to Instantiate.
This step is very important because, up until now, the changes and
new values haven't been transferred into the TestCasesInstances.
Only after Instantiation, we will have complete TestCases that
include the verification.
This can also be done by highlighting the Template and using the
keyboard shortcut CTRL+N, CTRL+I.
, ◉ Key Points for Modifying Templates.
Answer: 1. A verification Attribute has a value that Tosca uses to
verify against the SUT Output.
2. Check the Template for Reference before modifying it.
3. Use the Check Template function after modifying a Template.
◉ What are Conditions in Tosca?
Answer: Conditions instruct Tosca on when to use (or not to use)
certain TestSteps, TestFolders, or Values.
For example: A condition on a TestStep Folder will act as a rule for
when the content of the entire folder will be run.
A condition on a TestStepValue will just be applicable on that
specific Value.
◉ What are the Benefits of Conditions in Templates?
Answer: Conditions avoid Template repetition.
Using appropriately set Conditions means only one Template is
needed.
