refactor: rename end-to-end.rs to end_to_end.rs (#2015)
Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>pull/24376/head
parent
a79c0b4e75
commit
3bb32594ba
|
@ -125,7 +125,7 @@ There are end-to-end tests that spin up a server and make requests via the clien
|
|||
They are run by `cargo test --workspace` command but can be run exclusively with:
|
||||
|
||||
```
|
||||
cargo test --test end-to-end
|
||||
cargo test --test end_to_end
|
||||
```
|
||||
|
||||
Each server writes its logs to a temporary file and this is captured when the server shutsdown.
|
||||
|
@ -133,7 +133,7 @@ Each server writes its logs to a temporary file and this is captured when the se
|
|||
If you are debugging a failing end-to-end test, you will likely want to run with `--nocapture` to also get the logs from the test execution in addition to the server:
|
||||
|
||||
```
|
||||
cargo test --test end-to-end -- my_failing_test --nocapture
|
||||
cargo test --test end_to_end -- my_failing_test --nocapture
|
||||
```
|
||||
|
||||
If running multiple tests in parallel:
|
||||
|
@ -144,13 +144,13 @@ If running multiple tests in parallel:
|
|||
When debugging a failing test it is therefore recommended you run a single test, or disable parallel test execution
|
||||
|
||||
```
|
||||
cargo test --test end-to-end -- --test-threads 1
|
||||
cargo test --test end_to_end -- --test-threads 1
|
||||
```
|
||||
|
||||
Finally, if you wish to increase the verbosity of the server logging, you can set `LOG_FILTER` as you would for a normal IOx instance.
|
||||
|
||||
```
|
||||
env LOG_FILTER=debug cargo test --package influxdb_iox --test end-to-end end_to_end_cases::operations_api::test_operations -- --nocapture
|
||||
env LOG_FILTER=debug cargo test --package influxdb_iox --test end_to_end end_to_end_cases::operations_api::test_operations -- --nocapture
|
||||
```
|
||||
|
||||
### Visually showing explain plans
|
||||
|
|
|
@ -21,4 +21,4 @@ ENV TEST_INTEGRATION=1
|
|||
ENV KAFKA_CONNECT=kafka:9092
|
||||
|
||||
# Run the integration tests that connect to Kafka that will be running in another container
|
||||
CMD ["sh", "-c", "cargo test -p influxdb_iox --test end-to-end write_buffer -- --nocapture"]
|
||||
CMD ["sh", "-c", "cargo test -p influxdb_iox --test end_to_end write_buffer -- --nocapture"]
|
||||
|
|
|
@ -67,7 +67,7 @@ You can then run the tests with `KAFKA_CONNECT=localhost:9093`. To run just the
|
|||
tests, the full command would then be:
|
||||
|
||||
```
|
||||
TEST_INTEGRATION=1 KAFKA_CONNECT=localhost:9093 cargo test -p influxdb_iox --test end-to-end write_buffer
|
||||
TEST_INTEGRATION=1 KAFKA_CONNECT=localhost:9093 cargo test -p influxdb_iox --test end_to_end write_buffer
|
||||
```
|
||||
|
||||
### Running `cargo test` in a Docker container
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
//! This module contains "end-to-end" tests for the query layer.
|
||||
//! This module contains "end to end" tests for the query layer.
|
||||
//!
|
||||
//! These tests consist of loading the same data in several
|
||||
//! "scenarios" (different distributions across the Mutable Buffer,
|
||||
|
|
Loading…
Reference in New Issue