TestLens logo

TestLens

TestLens launches to accelerate Java and Kotlin pull request workflows

Every software engineer knows the problem: you’re done with the implementation of a feature, you’ve opened a pull request (PR), and now the build is failing. More often than not, some tests have failed, and you now need to figure out why. Was it your change? Did something in the environment change? Is the test flaky on the main branch as well?

Finding the root cause is tedious. The user interfaces of the PR and the test runners (GitHub Actions) are not well integrated and you have to scroll through long and noisy build logs. As a consequence, you often decide to “just” rerun the build without looking too closely. But rerunning takes a lot of time, pipelines are usually slow, costly and unnecessarily waste compute resources.

TestLens assists you in getting your pull requests merged faster. It posts an easy-to-read summary of all failed tests from all jobs as a PR comment and keeps it up-to-date as new results come in. You can see the reason a test failed right in your pull request without having to sift through the build logs. Moreover, it allows rerunning only those tests that have failed while skipping all previously successful tests. As a result, your rerun is finished much faster. If you’re convinced a broken or flaky test wasn’t caused by your changes, you can temporarily mute it to make the build pass.

This post marks the official start of the TestLens private beta! So far, the JUnit and GradleX open source projects have been onboarded, and are seeing great results. For example, here’s a PR comment posted by TestLens that shows a flaky test in a GradleX project.

TestLens currently supports JVM (Java, Kotlin, etc.) projects with tests running on the JUnit Platform via Maven or Gradle and CI builds running on GitHub Actions.

Prior to starting the private beta phase, we’ve already received onboarding requests from other open source projects which we’ll add in the coming weeks. If you’re interested in trying out TestLens as well, let us know.

The TestLens Team – Benedikt, Jendrik, and Marc