Repository navigation
Add tests for ongoing time entry check on manual creation - #65
Merged
Merged
Conversation
travismolick
added
blocked
Gawdl3y
force-pushed
the
test/time-entry-ongoing-guard
branch
from
October 10, 2026 21:19
2f4ae0e to
88e8a0d
Compare
Gawdl3y
approved these changes
Oct 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Adds regression coverage for the ongoing time entry check in
VolunteerController::storeTimeEntry, which #64 briefly broke and then fixed in a08bbda.stopmust return 409 on the second request, leaving exactly one ongoing entry. This fails on bed9ab4 (the second request returns 200) and passes on a08bbda.stopwhile another entry is ongoing must still succeed.The tests always send an explicit
startjust beforenow(), mirroring the real clock-in UI. They useRefreshDatabaseper-file, since it's disabled globally.