Summary
The updated test sidebar is great, but there are a few issues with it:
Steps To Reproduce:
- Run some tests in the sidebar/from a given test class
- Deploy any test class
- Observe that those results are invalidated and that the entire sidebar refreshes, which takes a while in larger orgs and makes it hard to keep track of incremental changes
Expected result
I'm open to opinions here. My ideal would be that the sidebar doesn't appear to refresh at all and that if you update a test method name, the old test disappears and the new test is added.
Those are the only times in which any kind of refresh is necessary - test addition and subtraction - as far as I can tell, so the existing behavior is confusing and makes it really hard to incrementally keep track of which tests have been run and are passing / which tests have been run and still need to be updated when vetting failures
Summary
The updated test sidebar is great, but there are a few issues with it:
the sidebar still does not have an easy way to only show test classes present in the workspace (which was the previous test extension's default). This makes working with dependent packages - or in any sandbox - also extremely challengingopened Apex Test: sidebar defaults to showing all tests in org rather than only tests in current working directory #7298 for this pointSteps To Reproduce:
Expected result
I'm open to opinions here. My ideal would be that the sidebar doesn't appear to refresh at all and that if you update a test method name, the old test disappears and the new test is added.
Those are the only times in which any kind of refresh is necessary - test addition and subtraction - as far as I can tell, so the existing behavior is confusing and makes it really hard to incrementally keep track of which tests have been run and are passing / which tests have been run and still need to be updated when vetting failures