Skip to content

Commit 7434d1c

Browse files
committed
Update elt-common readme testing section
1 parent 97921a2 commit 7434d1c

File tree

1 file changed

+4
-17
lines changed

1 file changed

+4
-17
lines changed

elt-common/README.md

Lines changed: 4 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,6 @@ to each pipeline.
88
Development requires the following tools:
99

1010
- [uv](https://docs.astral.uv/uv/): Used to manage both Python installations and dependencies
11-
- [docker & docker compose]: Used for standing up services for end-to-end testing.
1211

1312
### Setting up a Python virtual environment
1413

@@ -21,25 +20,13 @@ package in editable mode, along with the development dependencies:
2120
> uv pip install --editable . --group dev
2221
```
2322

24-
## Running unit tests
23+
## Running the tests
2524

2625
Run the unit tests using `pytest`:
2726

2827
```bash
29-
> pytest tests/unit_tests
28+
> pytest tests
3029
```
3130

32-
## Running end-to-end tests
33-
34-
The end-to-end (e2e) tests for the `pyiceberg` destination require a running Iceberg
35-
rest catalog to test complete functionality.
36-
The local, docker-compose-based configuration provided by
37-
[infra/local/docker-compose.yml](../infra/local/docker-compose.yml) is the easiest way to
38-
spin up a set of services compatible with running the tests.
39-
_Note the requirement to edit `/etc/hosts` described in [infra/local/README](../infra/local/README.md)._
40-
41-
Once the compose services are running, execute the e2e tests using `pytest`:
42-
43-
```bash
44-
> pytest tests/e2e_tests
45-
```
31+
See ["How to invoke pytest"](https://docs.pytest.org/en/stable/how-to/usage.html#usage) fo
32+
instructions on how to limit the tests that are executed.

0 commit comments

Comments
 (0)