Repository navigation
test(client): expect the start buttons on planned games of a live night - #395
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
.NET Test Results 2 files 2 suites 56s ⏱️ Results for commit 5cd2a97. |
|
SummarySummary
CoverageBoardGameTracker.Api - 97.8%
BoardGameTracker.Common - 96.4%
BoardGameTracker.Core - 96.7%
Default - 89.3%
|
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
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.
The full Playwright run on master (79f7e8a) had one failure out of 1475:
play-manage.spec.ts› "shows the header, the play actions and who is expected". #381 added a Start button to each planned game that has not been played, and the spec from #388 still expected only the game chips.The spec now checks the game chips and the two Start buttons separately. The spec file passes locally (53 tests).
🤖 Generated with Claude Code