Tricentis Tosca Review

Tosca CI: allows us to test when the code is deployed into the lower environment.


Valuable Features:

Tosca Continuous Integration (Tosca CI) - today's fast pace agile environment needs fast feedback. Working along with the development team and being able to test as soon as the code is available; gives the organisation an edge!

Tosca Continuous Integration allows you to exactly achieve that.

Improvements to My Organization:

We have implemented Tosca CI, it allows us to test as soon as the code is deployed into the lower environment. Automated sanity, smoke tests have been configured to run every time there is a code deployment. The sanity/smoke tests are triggered automatically from a build server. After the test finishes, a Junit result file is generated and fed back to the build server.

This saves us significant amount of time by avoiding additional co-ordination/follow-ups required for sanity/smoke test. 

Room for Improvement:

The Junit result file gets overwritten each time the build is triggered from Jenkins or Bamboo. It would be nice to have the result XML files stored.

Deployment Issues:

Only minor issues.

Stability Issues:

The connection between the CI client and remote machine dropped off when certain standard Tosca modules were used in the test cases.

Example: TC Send Key, TC Name To Buffer

Scalability Issues:

No issues so far.

Customer Service:

Customer service is reasonably good.

Initial Setup:

There were a few hiccups on the way with the configuration files. 

Disclosure: I am a real user, and this review is based on my own experience and opinions.
3 visitors found this review helpful
9 Comments
Orlee GillisConsultant

At the moment, how have you been managing the difficulties you've been having with files getting overwritten?

25 October 16
EdwinUser

Which software product is being tested by Tosca CI?

04 November 16
Manish Kum@rReal UserTOP 5LEADERBOARD

Hi Edwin,

Tosca CI(Continuous Integration) as the name suggest - it enables the tests to be executed directly from the build server. Which means tests can be run automatically as soon as there is a new code deployment. And after the execution has finished, Tosca CI generates an execution result and stores it onto the build server.

Tosca CI is can be thought to be a mechanism that starts the execution regardless of what software product or which type of tests are being tested.

Feel free to let me know if you have any further questions.

04 November 16
Manish Kum@rReal UserTOP 5LEADERBOARD

@Orlee- the result file gets overwritten each time but this does not impact our testing much as the results are only relevant for the current execution. If we still want to keep a stack of all the results then the files can be copied over to a different location.

04 November 16
Orlee GillisConsultant

Manish, thank you for the tip! Do you keep a stack of the results this way or do you only know that it's an option for those who want to?

06 November 16
User at a tech services company with 10,001+ employeesConsultant

i am trying to implement Tosca integration with bamboo, if i can get some input from you then its really helpful

14 December 17
User at a tech services company with 10,001+ employeesConsultant

Is there any way i can get more input on the same(tosca and bamboo integration)

18 December 17
User at a tech services company with 10,001+ employeesConsultant

@Manish Kum@r---->Need your help here.thanks in advance

18 December 17
Manish Kum@rReal UserTOP 5LEADERBOARD

Hi @reviewer789099 - how may I help you? Do let me know if you are faced with a challenge or just need the 'how to' about Tosca CI?

04 April 18
Guest
Sign Up with Email