Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 30 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -44,6 +44,36 @@ uv run pytest

If all is well, you should see the test run in the Test Engine section of the Buildkite dashboard.

## 🏷️ Filtering Tests by Tags

You can filter which tests to run based on execution tags using the `--tag-filters` option.

First, mark your tests with execution tags:

```python
import pytest

@pytest.mark.execution_tag("color", "red")
def test_red_feature():
assert True

@pytest.mark.execution_tag("color", "blue")
def test_blue_feature():
assert True
```

Then filter tests by tag using the `--tag-filters` option with `key:value` format:

```sh
# Run only tests tagged with color:red
pytest --tag-filters "color:red"

# Run only tests tagged with color:blue
pytest --tag-filters "color:blue"
```

**Note:** The `--tag-filters` option performs exact key:value matching. Only tests with the specified tag will be selected.

## 🎢 Tracing

Buildkite Test Engine has support for tracing potentially slow operations within your tests, and can collect span data of [four types](https://buildkite.com/docs/test-engine/importing-json#json-test-results-data-reference-span-objects): http, sql, sleep and annotations. This is documented as part of our public JSON API so anyone can instrument any code to send this data.
Expand Down
2 changes: 1 addition & 1 deletion pyproject.toml
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ build-backend = "hatchling.build"

[project]
name = "buildkite-test-collector"
version = "1.2.0"
version = "1.3.0"
description = "Buildkite Test Engine collector"
readme = "README.md"
requires-python = ">=3.9"
Expand Down
2 changes: 1 addition & 1 deletion uv.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.