git commits for readyAPI files
I wonder how other people handle git commits for their saved tests.
I have a few projects which hold 1000s of tests. We run them often and every time a file is executed - we get file changes to commit. And internal guids change which causes differences.
If I run those tests on one machine and a colleague is running the same branch on another machine, we often end up with 100s of conflicts.
Is there a set of files that we can set to ignore in the commit?
Is there a setting that prevents those GUIDS from changing while running the tests?
I know there is an option to run a tear-down script, which I have implemented in the past - it is not 100% solution and since my tests generate random data - I would like it to stay there until after they run so if I get a fail I will be able to investigate.
How do other people handle this? what does smartbear suggest?
Thanks
Smadar