New Test Track Release

22-03-2024 19:07

Towards the end of last year I did a blog post detailing how a new major release was coming for Test Track. Although it took me a bit longer to implement that I hoped, I can finally say its live and available for you to give it a try.

Want to see what’s new, then you are in the right place

New User Interface

A new user interface has been designed for viewing and creating test plans or test run steps. No longer is the annoying sidebar that takes up half the screen and covers the other steps. Now you can see the test steps along side the current step you are working on, making it simpler and easier to navigate.

You also get a new project overview providing a quick snapshot of how you project is going, such as how many automated test runs have been submitted, how many test runs contain flaky tests and how many test runs are in progress.

Automated Test Runs

You can now submit automated test runs from your CI/CD servers using the JUnit XML file format, which is a standard that most CI/CD support generating. This ensures all of your tests whether they are manual test runs or automated test runs are collected centrally in one location.

You can either use the API directly to submit your test run, or via our simple to use test-track-cli.

With it you get a nice shapshot view of all of the details such as how many tests have passed and failed, total number of tests and total skipped etc, along with the individual details of each test step.

Flaky Test Detection

Nobody likes a flaky test, if you are not familiar with the term, a flaky test is a test which flips regularly between pass and fail, causing a lack of trust between the test and development/testing team and potentially slowing your team down to a new release.

With Test Track, when a manual test run is completed, or an automated test run is submitted, an automatic flaky test check is performed across all steps in the test and the previous history, and a report is emailed to you highlighting the tests that are found to be flaky, or ones that have recovered.

If a test plan contains a flaky test, it is flagged and then each individual test within the test plan, or test run so you can easily find which tests are considered flaky and need improving.

There’s plenty more to come in the future, if you have any feedback, good or bad, I’d love to hear it, feel free to drop me a message at [email protected] or by leaving a comment on this post.

If you have any issues, you can also raise a support ticket at https://support.devso.io.