-
Notifications
You must be signed in to change notification settings - Fork 289
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
[UI Tests] Examine / address flakiness in History
tests.
#1551
Conversation
You can test the changes in simplenote-ios from this Pull Request by:
|
History
tests.History
tests.
@@ -38,6 +37,7 @@ class EmailLogin { | |||
enterPassword(enteredValue: password) | |||
app.buttons[UID.Button.logIn].tap() | |||
handleSavePasswordPrompt() | |||
waitForSpinnerToDisappear() |
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.
Not really a part of the fix, and not necessary, but it does not hurt, and does not occupy much time, since the function waits for the spinner to disappear. So, if the spinner was not there in the first place, it will be completed really fast.
History
tests.History
tests.
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.
Today I realized I hadn't set this repo up since my trial 😓 ❤️
- Xcresult file looks good
- Tests are passing locally
- I could notice
EmailLogin.handleSavePasswordPrompt()
working locally - CI is 🟢
|
||
echo "--- 🚦 Report Tests Status" | ||
if [[ $TESTS_EXIT_STATUS -eq 0 ]]; then | ||
echo "Unit Tests seems to have passed (exit code 0). All good 👍" | ||
echo "UI Tests seems to have passed (exit code 0). All good 👍" |
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.
Good catch! =D
Fix
History
tests demonstrated flakiness. E.g. here and here. This was not reproducible locally. The fix consists of two parts:xcresult
log file, so that it's actually copied as BK artifact. Without the log, it was not clear what was going wrong on CI.Six subsequent green executions is not a hard proof of the fix success, but this deserves a chance to be tested in action, IMO.
Test
xcresult
file.Review
Only one developer and one designer are required to review these changes, but anyone can perform the review.
Release
These changes do not require release notes.