-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ANDROAPP-6326] set default target SDK version #3730
[ANDROAPP-6326] set default target SDK version #3730
Conversation
Signed-off-by: andresmr <[email protected]>
40d0b20
to
0aecd71
Compare
Signed-off-by: andresmr <[email protected]>
e8468a6
to
f35d785
Compare
Signed-off-by: andresmr <[email protected]>
f35d785
to
a55b830
Compare
Quality Gate passedIssues Measures |
fun checkSyncWasSuccessfully() { | ||
val expectedTitle = InstrumentationRegistry.getInstrumentation() | ||
.targetContext.getString(R.string.sync_dialog_title_synced) | ||
composeTestRule.waitUntilAtLeastOneExists(hasText(expectedTitle)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this method I believe has a default time that throws an exception if not found, and is 1000 ms if not specified. I have seen tests fail due to the ocasional slow loading of the page other times this assertion was used, do you think it's a good idea to increase the time out to 2000 ms at least?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, it has a default time 1000ms, so it's the time that the workers are setting sync successful, why don't we try the default implementation and if it fails we can think on increment it?
No description provided.