⭐ Introducing a new command: poly test ⭐

[DavidVujic]

The Python tools for the Polylith Architecture now has a new command called poly test. As of this release, it is meant to be used with a sub-command: poly test diff.

This command is adding the possibility to identify bricks and projects that are affected by changes in tests. In its structure, the new command is very much like the existing poly diff command (that will display changed bricks compared to a git tag).

The poly test diff command will show you any affected bricks or projects when the automated tests have been updated. When changing a test that imports a brick, the command will report the brick as affected. The command can also report on the affected project(s), based on the affected brick.

It is available in the CLI v. 1.27.1 and in the Poetry plugin v.1.37.1. As of this version, tests are expected to live in a test folder at the workspace root when using the recommended loose theme. For users of the tdd theme, the tests are expected to be found in the brick test (the sibling to the src) folder.

Example usage:

# Poetry
poetry poly test diff

# CLI users, such as uv
uv run poly test diff

Affected bricks:

# Poetry
poetry poly test diff --bricks

# CLI users, such as uv
uv run poly test diff --bricks

Affected projects:

# Poetry
poetry poly test diff --projects

# CLI users, such as uv
uv run poly test diff --projects

For a programmatic approach, such as determining what to do in a CI, there are flags that will output a list of affected bricks or affected projects:

# Poetry
poetry poly test diff --bricks --short
poetry poly test diff --projects --short

# CLI users, such as uv
uv run poly test diff --bricks --short
uv run poly test diff --projects --short