Android Basics: Viewmodel and State in Compose

[myhency]

@Test
fun gameViewModel_Initialization_FirstWordLoaded() {
    val gameUiState = viewModel.uiState.value
    val unScrambledWord = getUnscrambledWord(gameUiState.currentScrambledWord)

    // Assert that current word is scrambled.
    assertNotEquals(unScrambledWord, gameUiState.currentScrambledWord)
    // Assert that current word count is set to 1.
    assertTrue(gameUiState.currentWordCount == 1)
    // Assert that initially the score is 0.
    assertTrue(gameUiState.score == 0)
    // Assert that the wrong word guessed is false.
    assertFalse(gameUiState.isGuessedWordWrong)
    // Assert that game is not over.
    assertFalse(gameUiState.isGameOver)
}

At the first time the app initialized, currentWordCount should be 0 not 1. Am I wrong?

[tugceaktepe]

Yes, you're right. I spotted it, too. Because init block in GameViewModel calls resetGame(). In this function, a new instance of GameUiState with shuffled word is created for _uiState. So, currentWordCount takes default value, 0. I'm sure this mistake will be fixed, soon.

[AAB999]

No, it is not fixed yet.... i just encountered the same issue while testing, and found the solution also by myself and thinking, maybe this fault is on purpose to test our understanding of the function because it is so easy to see?... :-)

[android-dev-lxl]

@tugceaktepe
@AAB999
@myhency

Could you please check now.
This should have been fixed!

[enikebraimoh]

@android-dev-lxl this has not been fixed on the Codelab it still states
val currentWordCount: Int = 0, val score: Int = 1,
when the object is created, currentWordCount should be 1 and score should be 0

[osuleymanova]

Hello @enikebraimoh,

Thank you for reaching out to us. The typo is fixed: