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.
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
Customer service is reasonably good.
There were a few hiccups on the way with the configuration files.
Which version of this solution are you currently using?