Answers
Question 1:
What is a Test Job in CRT (definition)?
Answer:
A set of test instructions indicating how and what to perform; used to configure assets to run,
execution configuration, and the robot for the task.
Question 2:
What does a Test Job do to your tests conceptually?
Answer:
Divides tests into several logical, smaller test processes executed one after another.
Question 3:
Can a Test Job exist without a Robot?
Answer:
No; a test job must be linked to a Robot (and that Robot is connected to a project).
Question 4:
What is tied to a test job when you execute tests in CRT?
Answer:
Tests, results, videos, etc. are all tied to the test job.
Question 5:
How can test jobs be executed (run options)?
Answer:
Manually, scheduled, or triggered from external sources using CRT API.
Question 6:
Where is it recommended to store test cases/files for a test job (note)?
Answer:
In Git (recommended) to keep a saved copy/version control (vs only in CRT).
Question 7:
Empty Test Job: what does it create and what's key about version
control?
Answer:
Creates a job with no pre-configured scripts;
includes tests/resources with templates; files are not version-controlled.