Issue#94 Grammatical issues: Core.Again
This commit is contained in:
parent
28e7638e7a
commit
13b27ac9d3
1 changed files with 5 additions and 5 deletions
|
|
@ -194,7 +194,7 @@ With this, looks like our Integration works correctly. Requests are called, prop
|
||||||
|
|
||||||
### 3. `localInputError`
|
### 3. `localInputError`
|
||||||
We have two expected errors, that are returned even before running requests, if the username or password is empty.
|
We have two expected errors, that are returned even before running requests, if the username or password is empty.
|
||||||
This two tests would be really similar, so let's do Parametrized tests.
|
These two tests would be really similar, so let's do Parametrized tests.
|
||||||
|
|
||||||
First we modify our method signature:
|
First we modify our method signature:
|
||||||
```kotlin
|
```kotlin
|
||||||
|
|
@ -339,7 +339,7 @@ If it would be cached, the test would be stuck, cause Loading wouldn't be emitte
|
||||||
|
|
||||||
## Conclusions
|
## Conclusions
|
||||||
With that we wrote our Integration tests.
|
With that we wrote our Integration tests.
|
||||||
There is no point of going over other integration test's in the core module, since the idea is captured, and nothing new could be shown.
|
There is no point of going over other integration tests in the core module, since the idea is captured, and nothing new could be shown.
|
||||||
If you want to give it a go, feel free, however consider using turbine for flow tests, cause it can be a bit tricky.
|
If you want to give it a go, feel free, however consider using turbine for flow tests, cause it can be a bit tricky.
|
||||||
|
|
||||||
What we have learned:
|
What we have learned:
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue