[Tests-Only] Fix replacement usernames #37706
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.
Description
When I do an acceptance test run with replacement usernames I get various test fails because some recently-added scenarios are not abstracting the username in the required places. So, for example, "Alice" is replaced with username "000" in PR #37506 but some
Then
steps fail because they expect hard-coded "Alice" when they should be expecting%username%
which will be substituted at run-time for the actual replaced username.REPLACE_USERNAMES
is defined. Show the username and user attribute replacements so that we know what was happening when we later lok at the log output.How Has This Been Tested?
CI in PR #37506 passes
Types of changes
Checklist: