add change assertion - enforce a change to a value #218
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.
Hi - initial pull request to see what people think of a change assertion. It's useful to avoid false positives where a test that previously caused an effect doesn't any longer, but this failure is masked by something else having caused it.
This is prone to false positives: if we break
addUser()
and merge it into a branch whereusers
started with a default user, we'd not get a failing test. With a change assertion we can be more specific about the change we want to see:Would avoid this issue.