Enable test_checkMissingTokenData #14316
Open
+44
−35
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.
I'm eager to actually have this test run and deliver value given various other bits of tinkering I've done, and plan to do around tokens.
I think there's some value to this test as is, especially around stating what desired state is even if the codebase isn't there today.
So;
@IgnoredRunning this locally, it passes on the tip of
master, albeit it does produce a number ofinfoandwarningmessages that are visible in the surefire reports. I think this is fine, and do not think it's worth addressing them all quite yet as some of these are tied up in the more fundamental and far reaching aim to move things that should be usingCreatureTokento doing that.