Skip to content

test: assert version command against __version__ - #20

Merged
jtdub merged 2 commits into
nextfrom
fix/version-command-test
Sep 22, 2026
Merged

jtdub merged 2 commits into
nextfrom
fix/version-command-test

Conversation

@jtdub

@jtdub jtdub commented Sep 22, 2026

Copy link
Copy Markdown
Contributor

Summary

test_version_command hardcoded assert "0.2.0" in result.output, so the version command test failed on the next branch once the package bumped to 0.2.1a0 — the command itself prints the version correctly.

Changes

  • tests/test_cli.py: import __version__ from the package and assert the command output contains it, instead of a hardcoded string.
  • CHANGELOG.md: entry under Unreleased.

Validation

  • tests/test_cli.py::test_version_command passes.
  • Full test suite: 39 passed.
  • ruff check, ruff format, and mypy clean on the test file.

The version test hardcoded '0.2.0', so it broke when the package bumped
to 0.2.1a0. Compare the output against __version__ instead so the test
tracks the actual package version.
@jtdub

jtdub commented Sep 22, 2026

Copy link
Copy Markdown
Contributor Author

@copilot resolve the merge conflicts in this pull request

# Conflicts:
#	CHANGELOG.md

Co-authored-by: jtdub <4454455+jtdub@users.noreply.github.com>

Copilot AI commented Sep 22, 2026

Copy link
Copy Markdown

@copilot resolve the merge conflicts in this pull request

Merged next into this branch. The only conflict was in CHANGELOG.md — both Fixed entries are now preserved under ## [Unreleased].

@jtdub
jtdub merged commit a0c614f into next Sep 22, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants