feat: basic test using Maestro + set up Maestro #67
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Unable to merge due to last minutes problem with the whole project. |
Aidasvenc
reviewed
Apr 13, 2024
Aidasvenc
reviewed
Apr 13, 2024
Aidasvenc
reviewed
Apr 13, 2024
|
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
End to end test that uses Maestro a tool that simulate a user utilisation.
Installation
We had to install it first (find informations here: https://maestro.mobile.dev/api-reference/)
Dependencies are necessary, including an android simulator. We used Orbit Expo to simulate on Android.
After building the APK of the app, testing with maestro is available running the following command:
maestro test test-maestro/registration-test.yaml (replace with the right path to the yaml test)
see screenshot here:
Contributions :
I enable a recording instruction and the end result can be seen here:
recording.mp4