Don't store passed tests in batches
Adam — Jan 02, 2018 11:20AM UTC
Currently when running our tests we store them as a batch. There's about 80 tests which constantly get stored in the result window each time the test is run, but this adds up so every time it runs it adds another 80 passed tests. This very quickly gets out of hand and you end up with thousands of tests results in the batch which slows the result window down to an unusable speed (over 5 minutes to load the batch and every click after that). This results in having to manually go delete thousands of passed tests while trying to avoid deleting the baselines.
Because of how we use eyes we only ever need to look if there's differences so it's pointless storing so many passed tests.
Is there a way to only keep the most up to date baseline and unresolved tests?
1 Community Answers
Yarden Naveh - Jan 02, 2018 at 12:39PM UTC
Thanks for reaching out.
I assume you are hard-coded setting a batch id for your tests. Therefore all the tests are going to the same batch instance.
A batch is planned to hold a single test cycle and not aggregate results from different cycles.
Do you only have one process that is executed per test cycle? If that is the case, simply remove the setting of the batch ID and this will resolve your problem.
If you have several executions per test cycle, we also have solutions for that – please elaborate more on your use case and I’ll be glad to assist.
If needed, I will also be happy to schedule a screen sharing session with you and take a closer look at your code and recommend some best practices.
Please let me know what works for you.