rename tests to describe purpose (and make single-run possible) - #396
Merged
Conversation
Tests with names like test3 cannot be easily run in isolation since "run AuthCest:test3" would also run test33 and test34
briskt
requested review from
ethancanne,
forevermatt,
jason-jackson and
mtompset
and removed request for
a team
July 27, 2026 02:37
hobbitronics
approved these changes
Jul 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixed
test3cannot be easily run in isolation sincerun AuthCest:test3would also runtest33andtest34. Note: Copilot created the names and I edited some of them before committing.PR Checklist
Release x.y.z - Summary of changes)make composershow