While running the same test for the second time in a smart UI environment, the image keep om adding in the same build?
Hii Miro,
When you’re faced with the problem of having too many images during successive test runs in your smart UI environment it’s important to know that the reason for this is that the build name is always the same. This means that you’re constantly adding images to your existing set, making it difficult to compare test iterations.
To solve this problem, you can make a small but effective adjustment to your build name before starting each test run by proactively changing the build name. By doing this, you’ll be able to differentiate between test cycles, avoiding the aggregation of images and allowing you to evaluate changes more accurately.
Adding this practice to your testing workflow will not only help you interpret test results more clearly, but it will also improve your testing processes overall. It encourages a more systematic approach, allowing you to analyze test outcomes in greater detail and identify specific issues within your smart UI environment more easily.
This small but effective change to naming conventions will help you keep track of your test results in a more organized and clear way, resulting in a smoother and more reliable testing experience.
Thank you for reaching out to us! We appreciate your interest and look forward to assisting you.