Automated tools are an essential part of the modern QA process and finding the right tools is a key objective for the QA Manager. The diverse spectrum of platforms within many organizations means that open source QA tools and UI-based testing products are sometimes too generic in nature and do not go deep enough on the IBM i platform to be effective. They focus mostly on reporting defects rather than identifying causes and helping to put things right immediately. Shifting quality left in the development process is a challenge because developers tend to leave testing until the end and then are pressed for time. In Agile/DevOps environments there is little time for code peer reviews, unit testing or regression testing and often there are insufficient metrics available to monitor code quality. Some legacy IBM i code can be difficult to understand and change and this compounds the code quality challenge.