![deck on the table](https://isorepublic.com/wp-content/uploads/2016/11/playing-cards.jpg)

### What is this project about?

This contribution is made to [gornanization/1k](https://github.com/gornanization/1k). If you would like to find more info - I strongly recommend reading [this post](https://utopian.io/utopian-io/@adasq/test) first.

### PR:
https://github.com/gornanization/1k/pull/24

### Details

![image.png](https://res.cloudinary.com/hpiynhbhq/image/upload/v1512816806/te4qmptd8ffbft2ooadc.png)

Since the [last change](https://github.com/gornanization/1k/pull/23), code coverage level have improved. Total gain for the contribution is **+10%** (**85%** for now). The scope of the change is set of two tests applied to public API covering both:

- user registration process,
- dealing cards and bidding preparation process.

As described above, this includes following phases coverage (notice phases marked with green colour):
![image.png](https://res.cloudinary.com/hpiynhbhq/image/upload/v1512815587/kbe13tw9v8tkqy0i7zvk.png)

What do we test? Phase transitions (and it's order),  action results (whether user action succeed or failed) and game logic pause mechanism (`next()` function which basically forces game logic to proceed).

What's more - and personally I think it's a massive feature of the project - using public API we can initialize game with specific state. Thanks to that, we do not have to walk through huge number of battle in order to test how does the API behaves in `GAME_FINISHED` phase. We can simply prepare state, which simulates the last round of the game and then test game finalization feature. It's huge - not only from unit testing perspective, but game players point of view as well. Imagine case, when we would like to take few steps back in game (for any reason, i.e. to re-shuffle cards again).

All the best, players!


<br /><hr/><em>Posted on <a href="https://utopian.io/utopian-io/@adasq/thousand-card-game-improving-code-coverage-1">Utopian.io -  Rewarding Open Source Contributors</a></em><hr/>