Digital.ai Continuous Testing could be better in certain areas, and I can share my experience-based view on what can be frustrating. One issue is device availability and queue delays during peak CI hours. Sometimes devices are busy, causing tests to queue and the pipeline to slow down unexpectedly, which is especially painful for large regression suites or tight release timelines. Improvements are needed in smarter auto-scaling of device pools and better priority-based scheduling. Additionally, execution speed variability occurs; the same test sometimes runs fast and sometimes slow, depending on device load and network latency, making results less predictable.

More stable execution environments and better performance isolation per session would help. Furthermore, debugging can still be indirect; even with logs or videos, I do not fully control the device as I would with local debugging, making it hard to pause and inspect live states or reproduce edge-case issues locally. More interactive debugging and improved local reproduction tools are necessary. Cost versus usage efficiency is another area of concern, as device cloud usage can be expensive and we sometimes have idle or inefficient tests that waste money. Improvements in usage analytics and cost optimization suggestions for smart test selection to run only impacted tests are areas where I believe Digital.ai Continuous Testing could improve.

Digital.ai Continuous Testing is a solid tool, but there are a few things that can be frustrating at times. One thing I noticed is that the initial setup and configuration can feel complex, especially when integrating it fully into the pipeline. It takes some time to get everything running smoothly. Also, sometimes the test results and logs are not as easy to navigate, especially when trying to quickly debug an issue. A more simplified or clearer view would really help in day-to-day work. There are also moments where test execution can be slower than expected, particularly with larger test suites or multiple environments. I think it could also improve in terms of UI/UX. It can feel cluttered and a more intuitive interface would make things easier, especially for new users. It is definitely powerful, but making it more user-friendly and smoother to work with would definitely make a big difference.

Digital.ai Continuous Testing is a strong platform overall, but there are a few areas where it could be improved. One challenge is that the initial setup and integration with CI/CD pipelines can sometimes be a bit complex, especially for teams new to automation. There can also be occasional delays when accessing specific real devices due to high demand. Additionally, debugging failed test cases in a distributed cloud environment can sometimes take extra effort compared to local testing. That said, these are relatively minor challenges, and the benefits in terms of scalability, speed, and coverage outweigh them.

Digital.ai Continuous Testing is a strong platform, but there are a few areas where it could be improved to make the experience even better. Especially when dealing with dynamic applications, while it integrates well with CI/CD tools, setting up and fine-tuning integration sometimes requires additional efforts compared to more plug-and-play solutions.

The integration process was good, but I've faced some challenges. Every time they release a new version, I find bugs in the UI and features. Sometimes, buttons don't work well. When this happens, I submit a ticket to technical support, but they often have to fix it in the next version.

I would like for changes to be interchangeable between the cloud device and the real device.

I would also like to see more videos and descriptions that could make installation more efficient.

I have been automating tests for many years on many things but not on mobile devices. The amount of time that I have spent on just figuring out how to use Experitest and get it to work was quite long compared to what I have been doing before. I spent the first two weeks just getting it started. It would be good to have some video explanation of how to use it on your devices and get started. Their online documentation is quite good and extensive, but it would be quite good to have some end-to-end examples demonstrated.