TOSCA TRICENTIS AS1 CERTIFICATION
Exams Questions and Answers Latest Versions
2025 Graded A+
1. Question: What are the main components of Tosca's architecture?
Answer: The main components include Tosca Commander, Execution
Server, Repository (TBox), Distributed Execution servers, and the
various Engine Packs for different technologies.
2. Question: What is the role of the Execution Server in Tosca? Answer:
The Execution Server manages and coordinates test execution, handling
test scheduling, distribution of tests to execution agents, and result
collection.
3. Question: What is DEX in Tosca? Answer: DEX (Distributed
Execution) is Tosca's feature that allows tests to be executed across
multiple machines or environments simultaneously, improving test
execution efficiency.
4. Question: What is an Engine Pack in Tosca? Answer: An Engine Pack is
a specific technology adapter that enables Tosca to interact with and test
particular technologies or platforms (like Web, SAP, Mobile, etc.).
5. Question: How does Tosca store its test assets? Answer: Tosca stores
test assets in a centralized repository called TBox, which can be file-
based or database-based (SQL Server).
6. Question: What is a Tosca Project? Answer: A Tosca Project is a
collection of related test assets (TestCases, Modules, TestSheets, etc.)
organized within a Workspace to test a specific application or system.
, 7. Question: What is the purpose of the Configuration section in Tosca
Commander? Answer: The Configuration section in Tosca Commander
is used to set up and manage environment settings, execution settings,
and engine-specific configurations.
8. Question: How does Tosca handle version control? Answer: Tosca
provides built-in version control capabilities for test assets and can also
integrate with external version control systems like Git or SVN.
9. Question: What is the relationship between Tosca Commander and
TBox? Answer: Tosca Commander is the client interface that allows
users to interact with the test assets stored in the TBox repository.
10. Question: What is the purpose of Tosca's Integration Platform? Answer:
Tosca's Integration Platform allows Tosca to connect and work with other
tools in the development ecosystem, such as ALM tools, CI/CD pipelines,
and issue trackers.
Installation and Setup
11. Question: What are the minimum system requirements for installing
Tosca? Answer: Minimum requirements include Windows operating
system, 8GB RAM (16GB recommended), 4-core processor, and 10GB
free disk space. Specific requirements may vary by version.
12. Question: What database options are available for Tosca's repository?
Answer: Tosca can use either a file-based repository or a database
repository using Microsoft SQL Server.
13. Question: What is the difference between a local and a shared repository
in Tosca? Answer: A local repository is used by a single user and stored
on their machine, while a shared repository is stored on a database server
and can be accessed by multiple users simultaneously.
14. Question: What is the purpose of the Tosca License Server? Answer:
The Tosca License Server manages and distributes license tokens to users
and execution servers, controlling access to Tosca features based on
purchased licenses.
15. Question: What types of licenses are available for Tosca? Answer: Tosca
offers various license types including Designer licenses, Execution
licenses, and more specialized licenses for specific features or
technologies.
, 16. Question: How can you update Tosca to a newer version? Answer:
Tosca can be updated using the Tricentis Update Manager, which checks
for available updates and manages the installation process.
17. Question: What is a compatibility package in Tosca? Answer: A
compatibility package ensures that different versions of Tosca
components can work together, allowing gradual upgrades of a Tosca
environment.
18. Question: What is the purpose of the Tosca Server Administrator tool?
Answer: The Tosca Server Administrator tool is used to manage Tosca
server components, including the License Server, Execution Server, and
repository settings.
19. Question: What should be considered before upgrading a Tosca
workspace? Answer: Before upgrading, consider creating backups,
checking for compatibility issues, reviewing the release notes for
breaking changes, and testing the upgrade in a non-production
environment first.
20. Question: How can you migrate from a file-based repository to a
database repository in Tosca? Answer: You can use the Repository
Migration Tool in Tosca to move test assets from a file-based repository
to a database repository, following a structured process provided by
Tricentis.
Section 2: Test Case Design
Creating Test Cases
21. Question: What are the different ways to create a test case in Tosca?
Answer: Test cases can be created manually from scratch, by importing
from external sources (like Excel), by recording user interactions, or by
generating them from requirements or models.
22. Question: What is a test step in Tosca? Answer: A test step in Tosca is
an individual action or verification point within a test case, representing a
specific interaction with the system under test.
23. Question: How do you add a verification point in a Tosca test case?
Answer: Verification points are added using the "Add Verification"
option in the test step editor or by using specific verification commands
like "Verify Element" or "Verify Value".
, 24. Question: What is the purpose of the "Buffer" feature in Tosca test steps?
Answer: The Buffer feature allows test steps to store values during
execution that can be used by subsequent steps, enabling data passing
between steps.
25. Question: How do you create a data-driven test case in Tosca? Answer:
Data-driven test cases are created by associating a TestSheet with a test
case and using parameters in test steps that reference columns in the
TestSheet.
26. Question: What is the purpose of the "TestCase Design" view in Tosca?
Answer: The TestCase Design view provides a graphical representation
of test steps and their relationships, helping visualize the test flow.
27. Question: How do you create a module in Tosca? Answer: Modules are
created by selecting "New Module" from the context menu, defining the
module parameters, and adding the required test steps.
28. Question: What is the "Copy to Library" function in Tosca? Answer:
"Copy to Library" allows users to save reusable test steps or sections as
modules that can be shared across multiple test cases.
29. Question: What is a condition in a Tosca test step? Answer: A condition
in a test step is a logical expression that determines whether the step
should be executed based on runtime values or parameters.
30. Question: What is the "Skip" property of a test step? Answer: The
"Skip" property allows a test step to be skipped during execution based
on a condition, without causing the test to fail.
Modules and Reusability
31. Question: What are the benefits of using modules in Tosca? Answer:
Modules promote reusability, reduce maintenance effort, ensure
consistency across test cases, and allow for centralized updates to
common functionality.
32. Question: What is the difference between a formal and an actual
parameter in a Tosca module? Answer: A formal parameter is defined in
the module itself as a placeholder, while an actual parameter is the value
passed to the module when it's called from a test case.
33. Question: How do you handle optional parameters in Tosca modules?
Answer: Optional parameters can be configured with default values in
Exams Questions and Answers Latest Versions
2025 Graded A+
1. Question: What are the main components of Tosca's architecture?
Answer: The main components include Tosca Commander, Execution
Server, Repository (TBox), Distributed Execution servers, and the
various Engine Packs for different technologies.
2. Question: What is the role of the Execution Server in Tosca? Answer:
The Execution Server manages and coordinates test execution, handling
test scheduling, distribution of tests to execution agents, and result
collection.
3. Question: What is DEX in Tosca? Answer: DEX (Distributed
Execution) is Tosca's feature that allows tests to be executed across
multiple machines or environments simultaneously, improving test
execution efficiency.
4. Question: What is an Engine Pack in Tosca? Answer: An Engine Pack is
a specific technology adapter that enables Tosca to interact with and test
particular technologies or platforms (like Web, SAP, Mobile, etc.).
5. Question: How does Tosca store its test assets? Answer: Tosca stores
test assets in a centralized repository called TBox, which can be file-
based or database-based (SQL Server).
6. Question: What is a Tosca Project? Answer: A Tosca Project is a
collection of related test assets (TestCases, Modules, TestSheets, etc.)
organized within a Workspace to test a specific application or system.
, 7. Question: What is the purpose of the Configuration section in Tosca
Commander? Answer: The Configuration section in Tosca Commander
is used to set up and manage environment settings, execution settings,
and engine-specific configurations.
8. Question: How does Tosca handle version control? Answer: Tosca
provides built-in version control capabilities for test assets and can also
integrate with external version control systems like Git or SVN.
9. Question: What is the relationship between Tosca Commander and
TBox? Answer: Tosca Commander is the client interface that allows
users to interact with the test assets stored in the TBox repository.
10. Question: What is the purpose of Tosca's Integration Platform? Answer:
Tosca's Integration Platform allows Tosca to connect and work with other
tools in the development ecosystem, such as ALM tools, CI/CD pipelines,
and issue trackers.
Installation and Setup
11. Question: What are the minimum system requirements for installing
Tosca? Answer: Minimum requirements include Windows operating
system, 8GB RAM (16GB recommended), 4-core processor, and 10GB
free disk space. Specific requirements may vary by version.
12. Question: What database options are available for Tosca's repository?
Answer: Tosca can use either a file-based repository or a database
repository using Microsoft SQL Server.
13. Question: What is the difference between a local and a shared repository
in Tosca? Answer: A local repository is used by a single user and stored
on their machine, while a shared repository is stored on a database server
and can be accessed by multiple users simultaneously.
14. Question: What is the purpose of the Tosca License Server? Answer:
The Tosca License Server manages and distributes license tokens to users
and execution servers, controlling access to Tosca features based on
purchased licenses.
15. Question: What types of licenses are available for Tosca? Answer: Tosca
offers various license types including Designer licenses, Execution
licenses, and more specialized licenses for specific features or
technologies.
, 16. Question: How can you update Tosca to a newer version? Answer:
Tosca can be updated using the Tricentis Update Manager, which checks
for available updates and manages the installation process.
17. Question: What is a compatibility package in Tosca? Answer: A
compatibility package ensures that different versions of Tosca
components can work together, allowing gradual upgrades of a Tosca
environment.
18. Question: What is the purpose of the Tosca Server Administrator tool?
Answer: The Tosca Server Administrator tool is used to manage Tosca
server components, including the License Server, Execution Server, and
repository settings.
19. Question: What should be considered before upgrading a Tosca
workspace? Answer: Before upgrading, consider creating backups,
checking for compatibility issues, reviewing the release notes for
breaking changes, and testing the upgrade in a non-production
environment first.
20. Question: How can you migrate from a file-based repository to a
database repository in Tosca? Answer: You can use the Repository
Migration Tool in Tosca to move test assets from a file-based repository
to a database repository, following a structured process provided by
Tricentis.
Section 2: Test Case Design
Creating Test Cases
21. Question: What are the different ways to create a test case in Tosca?
Answer: Test cases can be created manually from scratch, by importing
from external sources (like Excel), by recording user interactions, or by
generating them from requirements or models.
22. Question: What is a test step in Tosca? Answer: A test step in Tosca is
an individual action or verification point within a test case, representing a
specific interaction with the system under test.
23. Question: How do you add a verification point in a Tosca test case?
Answer: Verification points are added using the "Add Verification"
option in the test step editor or by using specific verification commands
like "Verify Element" or "Verify Value".
, 24. Question: What is the purpose of the "Buffer" feature in Tosca test steps?
Answer: The Buffer feature allows test steps to store values during
execution that can be used by subsequent steps, enabling data passing
between steps.
25. Question: How do you create a data-driven test case in Tosca? Answer:
Data-driven test cases are created by associating a TestSheet with a test
case and using parameters in test steps that reference columns in the
TestSheet.
26. Question: What is the purpose of the "TestCase Design" view in Tosca?
Answer: The TestCase Design view provides a graphical representation
of test steps and their relationships, helping visualize the test flow.
27. Question: How do you create a module in Tosca? Answer: Modules are
created by selecting "New Module" from the context menu, defining the
module parameters, and adding the required test steps.
28. Question: What is the "Copy to Library" function in Tosca? Answer:
"Copy to Library" allows users to save reusable test steps or sections as
modules that can be shared across multiple test cases.
29. Question: What is a condition in a Tosca test step? Answer: A condition
in a test step is a logical expression that determines whether the step
should be executed based on runtime values or parameters.
30. Question: What is the "Skip" property of a test step? Answer: The
"Skip" property allows a test step to be skipped during execution based
on a condition, without causing the test to fail.
Modules and Reusability
31. Question: What are the benefits of using modules in Tosca? Answer:
Modules promote reusability, reduce maintenance effort, ensure
consistency across test cases, and allow for centralized updates to
common functionality.
32. Question: What is the difference between a formal and an actual
parameter in a Tosca module? Answer: A formal parameter is defined in
the module itself as a placeholder, while an actual parameter is the value
passed to the module when it's called from a test case.
33. Question: How do you handle optional parameters in Tosca modules?
Answer: Optional parameters can be configured with default values in
