A. To be used as a direct replacement for regular test cases.

B. To store them in a library alongside their respective test data variations.

C. To convert them into workflows and publish them for execution.

D. To use them as base models for the test cases needed.

A. Passed executions are placed at the top.

B. Running and pending executions are placed at the bottom.

C. Manual executions are placed at the top.

D. Based on the date on which the execution was finished.

A. Validates the complete and fully integrated system. The purpose of a system test is to evaluate the end-to-end system specifications.

B. Evaluate the system's compliance with the business requirements and assess whether it is acceptable for delivery.

C. Individual units are combined and tested as a group. The purpose of this level of testing is to expose faults in the interaction between integrated units.

D. Individual units of a system are tested. The purpose is to validate that each unit of the system code performs as expected.

A. Manual and Scripted; invoked in Orchestrator only

B. Manual and Automated; invoked in Test Manager and Orchestrator.

C. Manual and semi-automated: invoked in Studio.

D. Manual and Automated; invoked in Test Manager only.

A. Code reusability should not be a consideration when creating test projects.

B. Try to reuse workflows as much as possible between projects.

C. Try to use libraries and object repository, whenever possible.

D. Try to use the project code base entirely independent of others.

A. It determines the timezone of your Orchestrator instance.

B. It allows to specify the timezone according to which the schedule is launched.

C. It allows to set up a default timezone for all test schedules.

D. It adjusts the test execution time according to the tenant's timezone.

A. Create separate test cases to cover each scenario during the execution.

B. Create one comprehensive test case that covers all scenarios in one execution.

C. Use the same test case, but execute it in different workflows.

D. Alter the workflow to ensure a single test case covers all scenarios.

A. Test cases from both Orchestrator and Test Manager.

B. Test cases that have been updated by your user, by specific labels, or the source.

C. Both manual and automated test cases from multiple Studio projects.

D. Only the test cases from Orchestrator.

A. The Test Case is used in multiple Test Sets.

B. Different project versions were used while publishing the test automation project.

C. The Test Case is linked to multiple Test Manager projects.

D. Different test automation project machine hosts were used while publishing.