The Summer months might appear to be winding down in the Northern Hemisphere, but that doesn’t mean the team at Launchable will stop bringing the heat. 🔥
It’s no secret that we’re big fans of increasing your team’s efficiency, which is why we’re so excited to share this month’s platform releases. August brings a total overhaul to the Flaky Tests page, with new weekly updates to flakiness scores. Also new this month are automatic links back to your CI logs and duration trackers for your flaky tests.
Flakiness scores are now updated every week
We just made a major update to the Flaky Tests page: scores are now calculated and updated every week!
Previously, scores were calculated across all test sessions, limiting you from seeing change over time. Now, you can check back each week to verify that your improvements are making a difference.
This change is part of a series of planned improvements designed to help you fight flaky tests in your test suite. Stay tuned for more like it!
🚀 Explore Flaky Test Insights
Automatic links back to Jenkins, GitHub Actions, and CircleCI
When viewing test results or other data in Launchable sometimes you want to jump back to where that test session actually happened -- namely, your CI server.
To make this easy, Launchable now links back to your CI logs automatically:
At launch, Jenkins, GitHub Actions, and CircleCI links are supported. Simply update to the latest version of the CLI to start using this feature!
🤝 Review Launchable Integrations
Total duration for flaky tests
Since flaky tests are often retried multiple times, this adds up to lots of extra time running tests.
To show this, the Flaky Tests page has a new column called Total Duration. This column shows the total execution time spent running a test in a given week:
This new value is useful for prioritizing which flaky tests to fix first.
For example, you might have a test that's very flaky (i.e. it has a high flakiness score) but either doesn't take very long to run each time, or it doesn't run very often, or both. In comparison, you might have a test that is less flaky but takes a very long time to run -- so you'll probably want to fix that first.