test: assert cli version against package __version__ - #1924
Merged
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Assert the CLI-reported version against
robocop.__version__instead ofimportlib.metadata.version("robotframework-robocop").Why
The old assertion compared the CLI output to the installed package metadata. With an editable install this drifts from the source (
src/robocop/__init__.py) whenever the version is bumped but the package is not reinstalled, producing a false failure that has nothing to do with the CLI.What changed
tests/test_cli.py: compare againstfrom robocop import __version__.from importlib import metadataimport.Tests
tests/test_cli.py::test_versionpasses; ruff + mypy clean.