Testing / TOSCA interview questions II

A testing process is designed within a software testing project and it consists of the following organizational units.

• Test planning.
• Test specification.
• Test execution.
• Test logging.
• and Test analysis.

The Tosca Requirements Management AddIn for Tosca Commander facilitates

• Organization,
• Development,
• Management,
• and Visualization

of various functional fields and requirements of software test projects.

With respect to the project administration, the Tosca Requirements Management AddIn creates a link between the following.

• Required TestCases,
• Created TestCases,
• Executed TestCases,
• and Test results.

When a workspace is created in TOSCA test suite, the Default objects could be automatically imported or manually using the import subset feature.

The Default objects are stored in the file standard.tce and is located under %TRICENTIS_PROJECT%\Toscacommander folder.

The components of the Default objects are,

• Standard modules that include TBox XEngines and TBox Automation Tools.
• virtual folders.
• and Standard Reports.

Tosca Commander WebAccess is a web application developed by Tricentis which allows Tosca Commander workspaces to be accessed/edited in a web browser without having to install Tricentis Tosca Testsuite on the local computer.

The host computer stores the TOSCA workspaces and browser client access the host's workspaces using WebAccess application hosted in a web server.

TC shell is used by TOSCA commander administrator and there are 2 different modes of starting TC Shell.

• The interactive mode, preferred by beginners to intermediate users, facilitates the user with support and options. The user has access to the full range of functionalities of the GUI version in Tosca Commander.
• The script mode, involves minimal interaction and meant for running the scripts in automated mode.

BDD is an agile methodology based software development process which is based on Test Driven Development.

BDD does not create executable test cases but executable documentation. In BDD, behavior and targets are specified as texts. This allows them to be tested as executable documentation. Requirements are mapped as user stories.

TOSCA supports the BDD in such a way that,

• A clear distinction is made between user stories (Requirements), scenarios (TestCase-Design Instances) and test cases.
• Scenarios are mapped in an easily readable format.
• All processes and actions are traceable.

Any project name should adhere to the below naming conventions in TOSCA.

• No special characters including _ (underscore), $.
• Maximum length is 16 characters.
• CamelCase naming.
• Ends with "Engine".

Any Namespaces will follow the below naming conventions in TOSCA.

• Rootnamespace has to be the project name.
• Must be project-root for COM-visible classes as there is no namespacessupport in COM.
• Namespaces can be chosen freely for .Net internal classes.