Hi everyone!
 
This is Dani, from Undefined Labs. We're a small startup focused on enhancing the development experience by improving the testing phase of the development lifecycle.
 
We're working on a new tool called Scope, which helps developers debug test failures, detect and manage flakiness, and brings about a 50-98% decreased testing time when executing your test suite.
 
Scope is totally free for OSS projects.
 
I was wondering if maintainers would be interested in adding Scope to the repository.
We'd be happy to give you a demo to see if Scope is something that would benefit Jenkins, and we'd love to get your feedback on the tool.
 
I've actually gone in and generated some results in Scope for your Jenkins core light tests.
The urls are open for everyone as long as you have a GitHub account. You can check it out here:
https://app.scope.dev/dashboard/b774c8da-2494-4ede-8d2f-b0321ff3cd7c/099d3377-7c7f-462a-b9c6-25669a6ce6ae/default/explore/inspect/c556bf446f60e873eccefed982b7fd2da3b628ab/
 
The installation is simple and fast, which you can see in this GitHub compare:
https://github.com/jenkinsci/jenkins/compare/master...scope-demo:install_scope
 
Because it can be hard to picture, I've included several screenshots of some of the current and future features of Scope that we think would be interesting and useful for contributors and maintainers.
 
Debugging a failing/flaky test (this is showing three test runs of a single test for a single commit, and the trace view of every request between multiple services and databases):

 
We have an Intelligent Test Runner that uses test impact analysis to only run the tests impacted by the recent code changes:

 
Managing flaky tests (a table of every flaky test, their duration, when they first exhibited flakiness, their flaky rate, and when the test last flaked - essentially helping you track and triage all of your flaky tests):

 
Getting testing insights through the Service dashboard (many teams want to keep master green but have no metrics around it; we show you how often master breaks, MTBF, and long it takes to repair, MTTR):

 
Finally, you can take a quick look at a demo repository we have, by clicking the following link:
https://app.scope.dev/dashboard/f0a213f0-b550-4bb0-a651-c1d5b9eff041/762ae391-d638-48b2-ba0e-bfe6bf5f99b9/default/explore/?item=feature-branch-3&tab=branches
 
Looking forward to hearing any feedback you may have and we'd be happy to give a quick demo of the tool to any maintainers .
Cheers!