saving executable and test suite runner builds

Ask general questions here.
mander95
Posts: 66
Joined: Tue Jun 21, 2016 7:35 pm

saving executable and test suite runner builds

Post by mander95 » Wed Jan 18, 2017 4:40 pm

Is there a way to store the executable and the test suite that was used in a test after it's executed into another folder? For example, I build a solution and it produces a new executable that's different from the previous one. Can I store or copy this executable to another folder like a software build?

krstcs
Ranorex Guru
Posts: 2683
Joined: Tue Feb 07, 2012 4:14 pm
Location: Austin, Texas, USA

Re: saving executable and test suite runner builds

Post by krstcs » Wed Jan 18, 2017 4:45 pm

You should be using a version control system. This will capture all of the actual file changes that are happening so you can rebuild whatever version of your tests that you need. There is then no need to store all of the executables multiple times with this setup because you can just roll back to a previous version and rebuild that instead of storing multiple copies of the same file.

Otherwise, you should probably be using a Continuous Integration (CI) solution like Jenkins, where you can have Jenkins store the artifact where you want after building.

If not, you could add a POST build action in your projects that would copy the artifacts somewhere, but this is a pain to manage and has to be done for each individual project. Jenkins is easier.
Shortcuts usually aren't...

mander95
Posts: 66
Joined: Tue Jun 21, 2016 7:35 pm

Re: saving executable and test suite runner builds

Post by mander95 » Tue Jan 24, 2017 5:14 pm

Added a post build action that solved the problem, thank you very much.