potiuk commented on issue #23083:
URL: https://github.com/apache/airflow/issues/23083#issuecomment-1112305537
> We want to run pytest in our container. Too run `docker exec ...pytest`,
the container needs to be running. Do we actually want `breeze tests` to spin
up the container?
Yes. This is how it was done before and this is also needed to run the tests
in CI (and how they are run currently).
Basically in CI we run multiple tests in parallel - and what we do we spin
multiple containers for that - each "group" of tests is run in a separate
container with separate databases and separate integrations if needed. So for
that we need to have a test command that
1) starts a docker-compose with container and all necessary containers.
Depending on the test type different containers are starting (for examplef when
you run integration, all the integration containers are started).
2) run the tests in the container (this is done by running the same thing as
entering shell but setting a few env variables - RUN_TESTS, TEST_TYPE I thiink
At later stage (when we reuse it in CI) - we should be able to run several
docker-compose in parallel (this is easy - by just setting different
docker-compose name)
All that done in `./breeze-legacy` and scripts that run test . For now just
focus on what `breeze-legacy` does.
Spinning containers is a very cheap operation in fact. so this is not e
problem to run them for tests.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
