[Feature Request] Support Migration Testing

[pascaldornfeld]

Is your feature request related to a problem? Please describe. As a tester I want to make sure that the app still works after going from version x to version y of my app. A typical testflow is:

• I install an already published app
• I generate some data to fill the app database
• I update the app to the version I want to test
• I check that the data from the old version is still visible

Describe the solution you'd like Support is needed to install apps during the testflow and including when running in maestro cloud.

Describe alternatives you've considered It is possible to install apks during tests with an appium testsuite and migrations can partly be tested with room integration.

Additional context none

[camoles]

Installing a different app in the middle of a flow would break the current model which assumes the flow applies to one app. One possible workaround for y our use case is to split the flow in two, one with the old app, and then the second with the new app, and run them one after the other.

[bartekpacia]

This scenario should be made possible by PR #1854, which aims to resolve issue #1665. Please take a look at it and let us know if you agree.

[github-actions[bot]]

Without additional information, we can't resolve this issue. We're therefore reluctantly going to close it.

Feel free to open a new issue with all the required information provided, including a minimal, reproducible sample. When creating a new issue, please make sure to diligently fill out the issue template.

Thank you for your contribution to our open-source community!

[Fishbowler]

@bartekpacia This is awaiting the PR to move through - I think the automation has been a little aggressive 😁

[bartekpacia]

Yeah, it's weird indeed. I'm gonna monitor the situation, thanks!

[github-actions[bot]]

Without additional information, we can't resolve this issue. We're therefore reluctantly going to close it.

Feel free to open a new issue with all the required information provided, including a minimal, reproducible sample. When creating a new issue, please make sure to diligently fill out the issue template.

Thank you for your contribution to our open-source community!