qTest and Tosca Integration Feature Matrix

The following matrix details the features that are available for qTest and Tosca integration based on the integration approach used to integrate the two products. Click a link in the Feature column to view an article that details additional information about that feature.

Feature	Description	Notes	Execution Method
			Tosca CI + qTest Jenkins Plug-in	Tosca CI + qTest Universal Agent	Native Integration: Tosca DEX + qTest Launch
Navigate across tools		Link to navigate between qTest and Tosca objects depends on the Tosca check box
Link Test Cases from qTest to Tosca	Test Cases are automatically created in the Tosca project's root folder. Test Cases from one qTest project will always be created into one Tosca project.	The Tosca check box on the qTest Test Case will force the Tosca DEX + qTest Launch execution method. If you want to execute with the Universal Agent, do not use this feature to link Test Cases from qTest to Tosca or from Tosca to qTest.
Link Test Cases from Tosca to qTest	You can select the qTest project and Module to create the test in. Test Cases in a Tosca project can be linked to more than one qTest project.	The Tosca check box on the qTest Test Case will force the Tosca DEX + qTest Launch execution method. If you want to execute with the Universal Agent, do not use this feature to link Test Cases from qTest to Tosca or from Tosca to qTest.
Tosca Test Cases in qTest marked with check boxes	In qTest, you can identify which tests are Tosca Test Cases by a check box.	The Tosca check box on the qTest Test Case is currently the flag to force the Tosca DEX + qTest Launch execution method.
Test Case changes to Test Step	If the Test Case is changed in Tosca, the next time the Test Case is executed, the Test Case will be updated with a new version.
Link TestEvents from Tosca to qTest	You can select the qTest project and Release or Test Cycle to create the TestEvent in.	Linking a Tosca TestEvent into qTest will allow the qTest user to execute that TestEvent using the existing Tosca configuration to distribute the TestEvent, such as to specific operating systems and browsers.
Schedule or trigger from qTest	Select the tests to be scheduled or triggered from qTest.	If the TestEvent was already linked from Tosca to qTest, the entire TestEvent will be executed.
Schedule or trigger from qTest	Select the tests to be scheduled or triggered from qTest.	Execution of the entire ExecutionList that is configured for the corresponding Universal Agent
Test Step details: description, execution result, actual result	After the execution, you can see the Test Step details when viewing the Test Run and the Test Case.
Log files on Test Log	The executed Test Run has an attached log file with more details on the passed and failed executions.	For the Tosca CI + qTest Jenkins Plug-in method, development for passed logs is complete, but is not yet released. The other two methods bring in logs for passed and failed Test Runs.
Distributed Execution (DEX)		Whether the TestEvent is linked from Tosca to qTest or the Tosca Test Cases linked to qTest are used to create Test Runs, which creates a TestEvent in Tosca, the tests can be executed in qTest using Tosca DEX to distribute with Tosca configurations, such as the browser or operating system.