Skip to content
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

Mobile app integration test CI #81

Open
vaind opened this issue Dec 2, 2019 · 4 comments
Open

Mobile app integration test CI #81

vaind opened this issue Dec 2, 2019 · 4 comments
Labels
good first issue Good for newcomers internal Internal enhancement/task, won't change public APIs

Comments

@vaind
Copy link
Contributor

vaind commented Dec 2, 2019

We should have a way to test ObjectBox runs on mobile (simulator) Android and iOS. From the quick look in the past I think our current tests (/test folder) can't be just executed on the target platform and we would rather need to have an app that instead runs the test suite itself. I've done this quickly in the past with the /lib/integration_test.dart. If this is the right approach, it should be moved to a separate dart/flutter project and run from CI for both mobile platforms (when iOS support #47 is merged)

@vaind vaind added enhancement New feature or request good first issue Good for newcomers labels Dec 2, 2019
@vaind
Copy link
Contributor Author

vaind commented Nov 10, 2020

Ideally, we should run the complete test suite (test folder) on all supported devices, if possible.

@vaind vaind added this to the 1.0 milestone Jan 21, 2021
@vaind
Copy link
Contributor Author

vaind commented Apr 1, 2021

I've partially prepared this: there's a flutter-integration-test job running in GH Actions. Right now, it builds release apps of both demo applications (sync & non-sync) on mac, windows and Linux.

TODOs:

  • run flutter drive: Flutter 2.0 has come out with a non-null-safe version of flutter_driver, basically turning it unusable, despite being built-in the SDK 🙄. As soon as a null-safe version of flutter_driver comes out (hopefully with Flutter 2.1?) we can have a look at the CI and see if it's an option to launch emulator/simulator. If so, flutter drive should just work and we can reenable it in ./objectbox/tool/integration-test.sh
  • still untouched - try running the whole test-suit in an app on device. I suspect this could be run with just lib/main.dart - looks like a Flutter app doesn't actually have to have any flutter code to be able to run? Let's see...

@vaind vaind removed this from the 1.0 milestone May 6, 2021
@vaind vaind added internal Internal enhancement/task, won't change public APIs and removed enhancement New feature or request labels May 13, 2021
@roiskhoiron
Copy link

Is this task already closed? @vaind

@greenrobot-team
Copy link
Member

@roiskhoiron No, this is still open. Also note that vaind no longer works on this project, so avoid tagging!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers internal Internal enhancement/task, won't change public APIs
Projects
None yet
Development

No branches or pull requests

3 participants