Breeze: Running integration tests in Breeze
See original GitHub issueWe should be able to run integration tests with Breeze - this is extension of test unit tests command that should allow to enable --integrations (same as in Shell) and run the tests with only the integration tests selected.
Issue Analytics
- State:
- Created a year ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Testing - Breeze | JS
Integration tests are appropriate because we are exploring how the parts of a Breeze app fit together. Module setup and teardown. QUnit can...
Read more >airflow/BREEZE.rst at main · apache/airflow - GitHub
You can run tests with breeze . There are various tests type and breeze allows to run different test types easily. You can...
Read more >Make Integration Testing a Breeze with API Mocking - Codit
In this demo we will run our tests from our favourite testing framework. During setup we will configure our responses in a storage...
Read more >Development and Test Environment for Apache Airflow
Airflow Breeze - Development and Test Environment for Apache Airflow. 5.5K views 2 years ago. Apache Airflow. Apache Airflow.
Read more >Testing Laravel Breeze Authentication - DEV Community
My plan for this post is to make some feature/unit tests to test the login and register functionality as well as improving my...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

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
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-legacyand scripts that run test . For now just focus on whatbreeze-legacydoes.Spinning containers is a very cheap operation in fact. so this is not e problem to run them for tests.
@potiuk Great. I think the general test command wil be covered by this issue not? This will then depend on the implementation of that issue. I can make a start on the
breeze testcommand and see later how we bring it together @Bowrna