run test in woolppecker ci#130
Conversation
ebb995e to
f899bcb
Compare
|
Here is how it can work:
Next steps:
|
|
Test run now in woodpecker CI, without any ports being exposed to the public. output.mp4 |
|
PRs from external forks need approval, tested in #187 |
eaec3c4 to
0a7d089
Compare
|
@guruz I see you updated Kaspresso to but it's incontibly with |
There was a problem hiding this comment.
Pull request overview
Adds Woodpecker CI plumbing to run Kaspresso-based Android integration tests against an emulator container, and updates the login UI-test selectors/flow to match the Keycloak login form used in CI.
Changes:
- Add a Woodpecker pipeline step to connect to an emulator via ADB and run a targeted
connected...AndroidTest. - Add docker-compose + env template for running an emulator (GPU) and Woodpecker agent on a dedicated network.
- Update integration-test login screen selectors and test setup to use the Keycloak form and a remote RC environment URL.
Reviewed changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated 4 comments.
Show a summary per file
| File | Description |
|---|---|
| opencloudApp/src/integrationTest/java/screens/LoginScreen.kt | Updates UIAutomator selectors for Keycloak login fields/buttons. |
| opencloudApp/src/integrationTest/java/eu/opencloud/android/LoginScreenTest.kt | Adjusts login test flow, URL target, and adds extra permission grants. |
| opencloudApp/src/integrationTest/docker-compose.yaml | Adds compose setup for emulator + Woodpecker agent networking and GPU configuration. |
| opencloudApp/src/integrationTest/.env.example | Adds example env vars for Woodpecker agent configuration. |
| gradle/libs.versions.toml | Adjusts the Kaspresso dependency version used by the project. |
| .woodpecker/integration-test.yml | Adds Woodpecker pipeline to run the integration test on emulator-labeled agents. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
6d1d9ea to
300ed83
Compare
related opencloud-eu/qa#82
running kaspresso tests in woodpecker CI
pipeline step is configured with the label:
platform: android-emulatorwoodpecker schedules the job on this dedicated server with kvm, where the Android emulator is available in docker and Kaspresso tests can be executed.
since we have only one device we use
WOODPECKER_MAX_WORKFLOWS=1which prevent parallel tests runningrunning existing espresso tests what need also server with kvm. note: Some tests was skipped in kaspresso integration tests #119 -> need fix
running android instrumented data tests
Result: