Keep list of specified tests
When choosing specified tests to do a validation, let's say from a comparison that was created from a bunch of drafts that were combined, the pop-up will show the specified tests that were chosen originally for those drafts that were combined. That is awesome and is exactly what I want.
The problem is the "Fetching test classes from Salesforce" then occurs automatically and replaces that list with the full list of test classes, and check the boxes for all of them, replacing my existing list. That means I have to go back and choose my list of specified tests again.
Amit Kulkarni commented
I also would love to see a feature like this implemented.
Since our org has thousands of tests, it's unfeasible for us to ever 'Run All Tests' for a deployment.
After I finish implementing some particular feature, I have no other option than to specify the tests I'd like to run.
When it's a smaller deployment (1-3 Apex Classes), the test detection feature (which I love by the way) works swimmingly.
However, as the deployment becomes larger, the detection mechanism becomes less reliable and begins to include unnecessary tests. Sometimes upwards of ~75% of the tests are irrelevant for the given deployment.
When this happens I manually remove the false positives from the list for the sake of a quicker deployment.
If the system could "remember" the tests from the last run, or allow me to save the list after deployment - it would help me out immensely.
With the Gearset recent update, it's good to see how AI picks up few test classes to run suggestion. But it would be great if we can save our own list of Test classes to run depending on my package.
Austin Turner commented
If I run a deployment and a unit test fails, then I go back and run the same deployment again after fixing the unit test I want the unit test selection process to be easier. Just keep my prior selection as the default instead of assuming I want to run all tests (which I NEVER want to do. EVER.)
If I wanted to run ALL tests, I would not have choses "run specified tests" to begin with, so the default of selecting all does not make sense.
Another suggestion would be to have a way to toggle to only run the unit test classes included in my deployment. Most of the time those are the only tests I want to run and sometimes I need to add a couple others in there, but it would be a much easier process.