Louvorg/ReaderForSelfoss-multiplatform
Louvorg/ReaderForSelfoss-multiplatform
3
2
Fork 2
Code Issues 16 Pull Requests Actions Projects 1 Releases 68 Wiki Activity

Repository Unit Tests #50

Merged
AmineB merged 38 commits from davidoskky/ReaderForSelfoss-multiplatform:repository_tests into master 2022-09-30 11:31:55 +00:00
Conversation 7 Commits 38 Files Changed 7 +12 -21
1 changed files with 12 additions and 21 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files
Showing only changes of commit 6cb4b35c93 - Show all commits

33
shared/src/commonTest/kotlin/bou/amine/apps/readerforselfossv2/repository/RepositoryTest.kt
View File

@ -46,14 +46,10 @@ class RepositoryTest() {
@Test
AmineB marked this conversation as resolved
AmineB commented 2022-09-27 13:54:00 +00:00
Review
Copy Link

This does not seem to do anything. Is it needed ?

This does not seem to do anything. Is it needed ?
davidoskky commented 2022-09-27 18:18:37 +00:00
Review
Copy Link

The test can fail if the repository initialization generates an error; this is just a very general case to identify if something in the repository initialization is broken.
All other tests would fail as well, but this will give you certainty that the point of failure is in the initialization.

The test can fail if the repository initialization generates an error; this is just a very general case to identify if something in the repository initialization is broken. All other tests would fail as well, but this will give you certainty that the point of failure is in the initialization.
AmineB commented 2022-09-27 18:29:28 +00:00
Review
Copy Link

The way I understand your comment is that sometimes, the repository can fail an throw an error.

This should not be handled in a unit test, but handled in the code.

The exception should be catched and handled there.

You can keep your tests, but the call should return something, and the tests should actually test something.

Same for the three following tests.

The way I understand your comment is that sometimes, the repository can fail an throw an error. This should not be handled in a unit test, but handled in the code. The exception should be catched and handled there. You can keep your tests, but the call should return something, and the tests should actually **test** something. Same for the three following tests.
👍 1
fun `Instantiate repository`() {
val success = try {
Repository(api, appSettingsService, connectivityStatus, db)
true
} catch (e: Exception) {
false
}
Repository(api, appSettingsService, connectivityStatus, db)
AmineB marked this conversation as resolved Outdated
AmineB commented 2022-09-28 06:41:59 +00:00
Outdated
Review
Copy Link

As mentionnend in my previous comment. The try catch must be in the code, not in the unit test.

As mentionnend in my previous comment. The try catch must be in the code, not in the unit test.
AmineB commented 2022-09-28 06:42:17 +00:00
Outdated
Review
Copy Link

Same for all the other try catch in here.

Same for all the other try catch in here.
davidoskky commented 2022-09-28 06:55:47 +00:00
Outdated
Review
Copy Link

I'm not sure how I would implement this test otherwise, I guess the repository should raise an exception during initialization then.

I'm not sure how I would implement this test otherwise, I guess the repository should raise an exception during initialization then.
AmineB commented 2022-09-28 06:57:14 +00:00
Outdated
Review
Copy Link

I guess the repository should raise an exception during initialization then.

Yep. That should be the case.

> I guess the repository should raise an exception during initialization then. Yep. That should be the case.
assertEquals(true, success)
coVerify(exactly = 1) { api.version() }
coVerify(exactly = 1) { api.stats() }
AmineB marked this conversation as resolved Outdated
AmineB commented 2022-09-27 13:54:06 +00:00
Outdated
Review
Copy Link

This does not seem to do anything. Is it needed ?

This does not seem to do anything. Is it needed ?
davidoskky commented 2022-09-27 18:18:48 +00:00
Outdated
Review
Copy Link

Same as above.

Same as above.
}
@Test
@ -61,28 +57,23 @@ class RepositoryTest() {
every { appSettingsService.getApiVersion() } returns -1
every { connectivityStatus.isNetworkConnected } returns MutableStateFlow(false)
val success = try {
Repository(api, appSettingsService, connectivityStatus, db)
true
} catch (e: Exception) {
false
}
Repository(api, appSettingsService, connectivityStatus, db)
AmineB marked this conversation as resolved Outdated
AmineB commented 2022-09-27 13:54:19 +00:00
Outdated
Review
Copy Link

This does not seem to do anything. Is it needed ?

This does not seem to do anything. Is it needed ?
davidoskky commented 2022-09-27 18:19:20 +00:00
Outdated
Review
Copy Link

Same as above.

Same as above.
assertEquals(true, success)
coVerify(exactly = 0) { api.version() }
coVerify(exactly = 0) { api.stats() }
}
@Test
fun `Instantiate repository with negative stats`() {
coEvery { api.stats() } returns SelfossModel.StatusAndData(success = true, data = SelfossModel.Stats(-100, -50, -20))
val success = try {
Repository(api, appSettingsService, connectivityStatus, db)
true
} catch (e: Exception) {
false
}
val repository = Repository(api, appSettingsService, connectivityStatus, db)
assertEquals(true, success)
assertEquals(0, repository.badgeAll)
assertEquals(0, repository.badgeStarred)
assertEquals(0, repository.badgeUnread)
coVerify(exactly = 1) { api.version() }
coVerify(exactly = 1) { api.stats() }
}
@Test