Build: Enable testing without magic comments (backports #46180) #46342
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.
Previously we only turned on tests if we saw either
// CONSOLEor// TEST. These magic comments are difficult for the docs build to dealwith so it has moved away from using them where possible. We should
catch up. This adds another trigger to enable testing: marking a snippet
with the
consolelanguage. It looks like this:This saves a line which is nice, I guess. But it is more important to me
that this is consistent with the way the docs build works now.
Similarly this enables response testing when you mark a snippet with the
language
console-result. That looks like:// TESTRESPONSEis still available for situations like// TEST: whenthe response isn't in the console-result language (like
_cat) orwhen you want to perform substitutions on the generated test.
Should unblock #46159.
gradle check?