-
Notifications
You must be signed in to change notification settings - Fork 3
Conversation
should update the tests. I think for the togeaggle swap test case I cut the log before the game ended so no changes needed there |
@@ -71,8 +71,8 @@ describe('hearthstone-log-watcher', () => { | |||
|
|||
gameState.should.deep.equal({ | |||
players: [ | |||
{id: 1, name: 'SpookyPatron#1959', status: '', turn: false, questCounter: 6, timeout: 75, cardCount: 16, secrets: [], position: 'bottom'}, | |||
{id: 2, name: 'SnarkyPatron#1301', status: '', turn: true, questCounter: -1, timeout: 75, cardCount: 18, secrets: [], position: 'top'} | |||
{id: 1, name: 'SpookyPatron#1959', status: 'WON', turn: false, questCounter: 6, timeout: 75, cardCount: 16, secrets: [], position: 'bottom'}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These values should have had 'WON' or 'LOST' before, because the dummy logs continues until the game ends.
Codecov Report
@@ Coverage Diff @@
## master #36 +/- ##
==========================================
+ Coverage 76.01% 78.04% +2.03%
==========================================
Files 13 14 +1
Lines 271 287 +16
Branches 50 50
==========================================
+ Hits 206 224 +18
+ Misses 45 43 -2
Partials 20 20
Continue to review full report at Codecov.
|
🎉 This PR is included in version 2.1.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
I don't think game-over is currently working
edit:
more specifically, the player's
state
value isn't set currentlycloses #38