Add support for running and debugging unit tests #1269
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR can be tested with the latest 2023.3 preview kit (build 245). The documentation has not been written yet, but here are some bullet points about how this new feature works that I have passed to our docs team:
objectscript.unitTest.relativeTestRoots
setting to tell the extension where your tests are located. A root in the Testing view is created for each element in this array.objectscript.unitTest.autoload
settings. All files in autoload folders that are in the tree of tests to run, up to theobjectscript.unitTest.relativeTestRoots
value for that Testing root, will be loaded on the server as well. Any documents that were created on the server by the loading will be deleted after the test run is complete. The autoload feature supports loading .cls, .mac, .int and .inc files, as well as legacy XML export files.