Integrating AI Tools Into the Continuous Testing Process.
Software Developer Engineer in Test Penn Interactive Miami, USA, Vladyslav Korol · The American Journal of Engineering And Technology · 2025
This paper utilizes AI tools to enhance the ongoing test cycle in a DevOps environment, thereby creating Metabase. This data architecture is robust and scalable, supporting a highly responsive release process. The project is vital since the releases have become more frequent; standard automation has already reached its limit, increasing the costs of maintaining scripts and, consequently, resulting in a significantly higher total cost due to the discovery of many more defects. The novelty of this work is grounded in an approach to choosing and applying AI tools through comparative analysis over available commercial and open-source platforms, supported by content analysis of empirical use cases and quantitative assessments from industry reports. Herein, a methodology is presented that consists of architectural solutions for data lake organization, continuous model training scenarios, and ML endpoints integrated into the CI/CD pipeline, which hosts Predictive Test Selection, as well as self-healing and test-case prioritization mechanisms. It narrates the creation of the prompt-engineer position and the connections between QA/ML experts and organizational facets. This paper discusses the application of clear AI measures for risk assessments. The final calls shown here indicate that intelligent automation enables reducing a regression set to a barely necessary size while maintaining 99.9% bug detection and minimizing false alert failures. This, in turn, leads to improvements in MTTR and TCO quality. TestPilot and FlakeFlagger verify Meta’s practices; furthermore, it is anticipated that forecasts will retain a CAGR of 20.9% in the global AI testing market growth. Solution maturity, encompassing both SaaS and on-premises models, offers a flexible choice to regulated industries. Metabase architecture is shown in which raw and processed data are kept separately to ensure timely model retraining as well as to minimize computational costs. This article will be helpful for software architects, QA managers, DevOps teams, and ML engineering specialists involved in building scalable and resilient testing architectures.