Page 1 of 1

saving executable and test suite runner builds

Posted: Wed Jan 18, 2017 4:40 pm
by mander95
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?

Re: saving executable and test suite runner builds

Posted: Wed Jan 18, 2017 4:45 pm
by krstcs
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.

Re: saving executable and test suite runner builds

Posted: Tue Jan 24, 2017 5:14 pm
by mander95
Added a post build action that solved the problem, thank you very much.