-
Notifications
You must be signed in to change notification settings - Fork 380
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
Make all current failing Espresso Tests pass #704
Comments
@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 😅 . Please label it as available |
My UI testing is not very good as well 🙈 |
Hello @devansh-299 |
@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 |
@rpattath Hey! Is this issue supposed to be closed too since we're opening smaller UI Espresso test issues already? |
We could split this up as well, there are about 8 tests that are failing. 1 test for the |
@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 Let me know if any changes needed. |
All sign up tests are passing but the login tests need to be changed as discussed on Zulip. |
This issue should be updated as currently we have removed the Travis CI from our code |
@kartikeysaran nice catch. @devansh-299 can you update the issue? |
Actually, at the time it was travis CI, changing the description not mentioning travis would not be true. This issue still represents the major priority which is having tests passing. |
@epicadk @isabelcosta if Travis CI has been removed and if needed, I can update the description of this issue to meet the current status of UI tests. Please let me know if any changes are to be made. |
@isabelcosta @epicadk Any updates on this ? Let's get this over with ! |
Yes the prs have been created they only need to be reviewed. |
@epicadk Then, I'll review them in the coming days. Let's get this issue over with, since this issue has been opened for way too long now ! |
Thanks. Will update about them on Zulip. |
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.html
Expected 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.
The text was updated successfully, but these errors were encountered: