Hey all,
I have a question regarding using Ranorex with source control & in a continuous integration environment.
I know that when you use Source control & CI, it is normal that when you change something in the Application Under Test or in your Ranorex project that it gets commited to the source control & automatically build by CI and that the tests can be automatically run by the CI also.
However, I've got a specific situation that I don't know how it is handled.
When there is new functionality planned and you prepare your test case in Ranorex. That already gets commited to Bamboo, but what if that new functionality is not committed yet? The test case will fail normally, right? because whenever you commit a change of your ranorex project, it gets automatically build & run.
How to prevent this?
Thanks,
Bart
Ranorex with source control & CI (Bamboo)
- Support Team
- Site Admin
- Posts: 12002
- Joined: Fri Jul 07, 2006 4:30 pm
- Location: Graz, Austria
Re: Ranorex with source control & CI (Bamboo)
Hello Bart,
Inside Bamboo you can configure the build strategy. It seems in your case a commit triggers the build and run event. There are many different options you can choose in the build strategy settings.
If changing the build strategy is not possible, you can also think of not committing the test for this feature.
Please let me know if I don't understand your question correctly.
Sincerely,
Bernhard
Inside Bamboo you can configure the build strategy. It seems in your case a commit triggers the build and run event. There are many different options you can choose in the build strategy settings.
If changing the build strategy is not possible, you can also think of not committing the test for this feature.
Please let me know if I don't understand your question correctly.
Sincerely,
Bernhard
Re: Ranorex with source control & CI (Bamboo)
Hi Bernhard,
Thanks, this fully answers my question!
Kind Regards,
Bart
Thanks, this fully answers my question!
Kind Regards,
Bart