You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some orgs have massive test suites that are VERY slow. If I'd like to deploy without running the full suite I can specify which tests classes to run, but figure out which ones will get me to 75% code coverage for everything in my package is nearly impossible without first running the full test suite.
Perhaps the test runner could store data on which tests classes touch which apex classes and triggers along with the percent of the code they cover. With that data we could expose an endpoint we could use with an sfdx plugin to make a best guess at what test classes to use to deploy a specific piece of code.
The text was updated successfully, but these errors were encountered:
Some orgs have massive test suites that are VERY slow. If I'd like to deploy without running the full suite I can specify which tests classes to run, but figure out which ones will get me to 75% code coverage for everything in my package is nearly impossible without first running the full test suite.
Perhaps the test runner could store data on which tests classes touch which apex classes and triggers along with the percent of the code they cover. With that data we could expose an endpoint we could use with an sfdx plugin to make a best guess at what test classes to use to deploy a specific piece of code.
The text was updated successfully, but these errors were encountered: