Fixing Update Logic

[ManasMalla]

1. On validating the last question, when we don't pick a new question, don't increment the currentWordCount. Updating the currentWordCount, the value updates to 11, where the max_number_of_questions is 10 and hence the test fails.
2. When initializing the ViewModel and setting up the first question, increment the currentWordCount as 1, else the status shows 0 out of 10.

Then the test cases given in the codelab work out of the box.

[dan-scott-dev]

1. On validating the last question, when we don't pick a new question, don't increment the currentWordCount. Updating the currentWordCount, the value updates to 11, where the max_number_of_questions is 10 and hence the test fails.
2. When initializing the ViewModel and setting up the first question, increment the currentWordCount as 1, else the status shows 0 out of 10.

Then the test cases given in the codelab work out of the box.

I think the bug is in the test, not in the main app code.

I think the test needs to be updated to:

 // Assert that current word count is set to 0.
  assertTrue(gameUiState.currentWordCount == 0)

In section 2 (App Overview), it says that "the app displays the word count, which is the number of scrambled words played in the current game" - which to me implies that it does correctly show 0 when starting, because you haven't yet played (past tense) a word yet, and in this case I would expect it to show 9 of 10 when I'm on the last word of the game (though intuitive this may be).