Describe the bug
After updating the .travis.yml in the PR #696 - link, many UI tests are failing (detailed report is here). The tests themselves or the code needs to be updated so that the tests do not fail and ultimately the build.
To Reproduce
Steps to run the tests locally
./gradlew clean build connectedAndroidTest --stacktrace../mentorship-android/app/build/reports/androidTests/connected/index.htmlExpected behavior
The Espresso tests shouldn't have failed
Smartphone (device on which the tests ran):
Additional context
Add any other context about the problem here.
@devansh-299 thank you for creating this :) Are you interested in working on this, or leave it for another contributor? Either way is fine, i just want to know if it should be assigned to you or labeled as available
@isabelcosta My experience with UI testing is not so good :sweat_smile: . Please label it as available
My UI testing is not very good as well 馃檲
Hello @devansh-299
Can you please explain the issue?
I do not quite understand it.
@devansh-299 Could you please add a few resources so that contributors can take this up? Thanks
@anna4j I tried to change the title to make this more clear, this is about making the tests which are failing pass.
@devansh-299 does this command./gradlew clean build connectedAndroidTest --stacktrace run the Android Espresso tests (user interface tests)?
@rpattath Hey! Is this issue supposed to be closed too since we're opening smaller UI Espresso test issues already?
@anna4j no this is for the current failing tests which is a still an issue. This issue was closed and broken down to smaller issues for new espresso tests to be added.
Hi. @rpattath @anna4j . I'd like to take up the task. Can I be assigned this issue ?
We could split this up as well, there are about 8 tests that are failing. 1 test for the SignUpActivity and 7 tests for the LoginActivity
@iofall Yes. We can make one issue for Signup tests and one for login tests
@iofall that is a nice idea :) if you could create those issues and link it here in a comment that would be amazing
@isabelcosta I have created these issues #868 and #918. Sorry I got late for this. Initially, I was planning on creating individual issues for each failing test, but that increased the complexity. Additionally, I discovered that some of the tests run successfully when run individually but fail when run as a whole. So I have just separated this issue into LoginActivityTest and SignUpActivityTest.
Let me know if any changes needed.
@iofall I think the tests are now fixed, can you or anyone else confirm that all tests are passing please?
Also, you did an amazing job separating the issues, that helps a LOT @iofall 馃憦 馃帀 Thank you so much for helping out!
@iofall I think the tests are now fixed, can you or anyone else confirm that all tests are passing please?
Also, you did an amazing job separating the issues, that helps a LOT @iofall 馃憦 馃帀 Thank you so much for helping out!
All sign up tests are passing but the login tests need to be changed as discussed on Zulip.
Most helpful comment
We could split this up as well, there are about 8 tests that are failing. 1 test for the
SignUpActivityand 7 tests for theLoginActivity