You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The .gitlab-ci.yml already contains a command that starts the integration tests. However, after running the command, no tests are executed - the log stops at Application finished.. When starting chromedriver with the --verbose flag, one can see that the output differs from when integration tests are executed locally. As executing the integration tests also does not work from within the Docker container when testing it locally (same behaviour), something seems to be amiss - so it should not be an issue with the GitLab CI.
Executing the very same commands (to start the chromedriver and flutter drive) locally, without a Docker container, works as expected. Some investigations are necessary.
In GitLab by @11775820 on Aug 14, 2021, 14:37
The
.gitlab-ci.yml
already contains a command that starts the integration tests. However, after running the command, no tests are executed - the log stops atApplication finished.
. When startingchromedriver
with the--verbose
flag, one can see that the output differs from when integration tests are executed locally. As executing the integration tests also does not work from within the Docker container when testing it locally (same behaviour), something seems to be amiss - so it should not be an issue with the GitLab CI.Executing the very same commands (to start the
chromedriver
andflutter drive
) locally, without a Docker container, works as expected. Some investigations are necessary.Inspiration for the CI job: https://gitlab.com/nicolalandro/flutter_test_app/-/tree/master. Maybe we need to have a look at the Docker image used there.
The text was updated successfully, but these errors were encountered: