The tool runs on a host and triggers “risky” jobs every two hours. It uses two subcomponents to determine which jobs are better suited for testing at that point in time: Hourglass Bug Predictor and Hourglass Code Risk Analyzer. Hourglass Bug Predictor uses Machine Learning to train a K-Star model that integrates with Jira. Using bug history in Jira, and defining areas of code based on components, labels, priorities, and custom fields, it uses that historical data to train the Machine Learning model which then predicts the potential number of bugs that can occur in the next week given the Jira data that defines those areas. The results are processed and associated with a given test automation job.
Hourglass Code Risk Analyzer integrates with Github or Bitbucket to track source code changes and commits and runs statistical data analysis, like machine learning algorithms, to associate source code files and folders with a risk assessment score. The files and folders of the source code are also associated with a given test automation job.
The resulting data from these two tools is normalized and consolidated, and since each are associated with specific automation jobs in you CI/CD pipeline, it will then use REST APIs to remotely trigger the top X jobs, in either Jenkins, TeamCity, (or other pipeline jobs that can be triggered with a URL), to run at that time.