-
-
Notifications
You must be signed in to change notification settings - Fork 907
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
Add Test Suites #597
Comments
Looks good. From which module do you think we should start with the test cases? |
@Swati4star Hey Swati, I started doing experimental testing on the Login Screen and Sign-up Screens, so we might want to start doing testing with the UI first using Espresso and automated testing. I used the method here: https://medium.com/@akifev/android-automation-testing-getting-started-with-espresso-a6f8cb50746a |
Hi! Can I give it a try to write some Espresso tests? |
@Komachka Which module do you wanna pick up for writing test? |
May I be assigned to this? |
Currently, there is no UI testing or functionality testing for TravelMate. It would be a good idea to start adding testing suites to the app so that it becomes more maintainable in the future. It would be also a good practice for people that wants to contribute to an open source project but they're at lost at where to start, this way they can slowly learn about the project by creating test cases for certain types of behaviours. Here's a good starting point for writing test cases in Android.
How
We can start by dividing the type of testing cases that can be done: UI Tests, Integration Tests, Unit Tests. We can start by writing small test cases first.
For UI:
We can use Espresso testing suite as recommended on this page for UI Tests.
For writing small Integration Tests and/or Unit Tests:
An example of how to write Integration Tests and Unit tests: http://robolectric.org/
Would you like to work on the issue?
I can start working on this issue. Others can help by doing their own Pull Requests.
The text was updated successfully, but these errors were encountered: