e2e migration test on PR targeting master - Githubissues

lydavid / MusicSearch

An Android app for browsing songs, artists, and anything related to them

Apache License 2.0

18 stars 0 forks source link

e2e migration test on PR targeting master #973

Open lydavid opened 4 days ago

lydavid commented 4 days ago

[x] gco master
[x] install app
[ ] maestro click through all screens[^1]
[x] gco release branch
[x] install app again
[ ] maestro click through all screens again

This is all based on the assumption that between GHA steps, we maintain the same AVD. Otherwise, each time we install our app, it will be a fresh install, which will not let us test that a migration from the master branch to the release branch worked without crashing. Confirmed with https://scans.gradle.com/s/6ulorrahmvalo/timeline and https://scans.gradle.com/s/asm2laxnfiir2/timeline

[ ] workflow that goes for all screens will only run on releases
[ ] copy/paste simpler workflow that runs a subset of these tests for each PR to replace current test-e2e.yml

[^1]: Because we run maestro test with $HOME/.maestro/bin/maestro test .maestro, the test suite will need to exist already on master.

lydavid commented 4 days ago

Not able to see the evidence of previous run in https://github.com/lydavid/MusicSearch/actions/runs/9726640692

[x] retry with maestro