Sergii L.

With all my new clients I face the classic situation of "regular test automation" which is rarely fully successful. I can give you some tips on how to find a better approach which I have formulated based on my past experience. Very often automated test cases are a waste of effort due to failed attempts to get added value for the project. All your "regular static scripts/suites" become outdated and irrelevant immediately after the first successful execution. Measurable additional value is achieved only by writing new scripts. Then, you spend more time updating scripts than getting useful information from their execution. In addition, due to the use of some available/popular frameworks, you also face the situation where it is not possible to fully automate test cases due to certain limitations of the chosen framework. So in addition to all these problems, some really important e2e cases still have to be tested manually. All available frameworks are only suitable for creating a simple sequence of a few static actions. True end-to-end testing with a 2-4 hour test runs covering all aspects of the application is impossible. But this is proven to be possible with what I offer, and each such test session is dynamic, unique and adds additional value to the project because of that. You will be able to cover many cornercases and test cases which are currently marked as "not automatable", since instead of static repetitive actions, a set of defined and interconnected requiremnets/expectations is used for creation of user actions sequence. In essence, you get requirements formulated in executable code, which allows you to test your application as close to how a real user will use it as possible. And, there's no AI involved, it's all completely under your control. No dendencies from external random noice generators.