Simplify soft assertion example and narrative #2
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.
Problem
When doing the exercise on soft assertions, I found it confusing how to correct the source code, because there were multiple bugs and it wasn't clear what the solution wanted us to do.
The bugs were:
Also, the solution was a bit overcomplicated (
setUTCMonth
handles year changes, i.e you can dotoday.setUTCMonth(20)
to set it to 20 months after the first day of that year), which I think brings the attention away from vitest and soft assertionsProposed solution
Let's simplify the logic so that the bug is a bit more straightforward to fix:
endAt
propertyGoing further
Maybe we'd want a test for the
TrialPlan
to guide the students further / provide more context?