[NFC/Unit test] - Fix secondary issue with case token consistency test #21369
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.
Overview
Intermittently failing test
Before
e.g.
After
Technical Details
api3 case create calls CRM_Case_BAO_Case::create to create the Case record, and stores it in $caseBAO. It then calls the xmlprocessor to populate the timeline, which via activity triggers updates case.modified_date. Then it returns the $caseBAO from before that as the api result. If there's a split-second delay then $caseBAO['modified_date'] won't match the latest modified_date, which is what the evaluated token uses.
Comments
Is test