This site requires JavaScript to be enabled
IE BUMPER

Logo

Dear Tricentis qTest users,

If you would like to submit a Tricentis qTest ticket,

please use this support request form.

Tosca Version
IncidentLookup using list
Language
How can we help?

Solution Suggestions

Please enter your question to get suggestions.
  Help
IE BUMPER
Categories
Boolean Operators
OR or vertical bar symbol (|)
Finds a match if either the terms exist in a document (a union using sets).
AND
Finds a match if both terms exist in a document (an intersection of sets).
NOT, minus (-), or exclamation point (!)
Excludes documents that contain the term after NOT (a difference of sets).
Wildcards
Asterisk (*)
The asterisk symbol performs a multi character wildcard search.
Percent sign (%)
The percent sign performs a single character wildcard search.
Phrases
Quotation marks (")
Use quotation marks to search for an exact phrase with multiple terms.
For examples and more information look at our Knowledge Base: Advanced Search On The Support Portal

How to integrate ToscaCI in Microsoft TFS 2015

This article describes the necessary steps to run Tosca Testcases from your Team Foundation Server 2015 Build Process


Situation

Microsoft Team Foundation Server 2015 is a commonly used platform for development and build. Within a Continuous Integration lifecycle it is mandatory to run your automated tests after each checkin. For this scenario Tricentis provides the Tosca Continuous Integration solution.

Solution

Within your TFS WebInterface open up your Project view and click onto the build tab and go to Edit mode

 

Within this view all build steps for your project are listed. To use ToscaCI we now add another build step of type 'Command Line'

This 'Command Line' step is responsible for calling ToscaCI Client with the corresponding parameters. Therefore we edit the step accordingly and give it a readable name (to create a JUnit test result we additionally use the parameter '-t' with the value 'Junit')

After adding the step to run our ToscaCI tests, we add another one of type 'Publish Test Results' to publish our ToscaCI test results after finishing the execution

We choose 'JUnit' as Test Result Format and point to the location of the result.xml file

 

 

0 0

Gokul S2

Created: 2017-01-25 08:15:06

Thanks for the document. Can we use it when TOSCA client and TFS are not installed on same machine.

For Eg. if the machine from which I am doing the check in does not have TOSCA.

Thomas Stocker

2017-02-09 06:49:59

@GOKUL S2,

yes you can. ToscaCI consists of a client which is available for Windows and Linux and ment to be kicked off by the build server and a remote component which act as an execution agent on a certain Tosca machine.

Besides that, you also can use several execution machines for you build by sending the execution request from your ToscaCIClient not to one specific execution machine, but rather to ToscaDistributedExecutionServer who then can distribute the tests among all agents connected.

0 0

David Fortin

Created: 2019-11-07 14:37:32

Is there more information about setup to point it at a specific machine , rather than utilize Distributed Execution? Or Is DE the preffered method?

Specifically I am interested in how you would specify what target machine to run the test on if not utilixing DE.

Thank you!

IE BUMPER

Tosca is the perfect solution

Optimize - Manage - Automate

Download Trial