Repository navigation
make tests survive a release - #223
Merged
Merged
Conversation
Signed-off-by: Panos Vagenas <pva@zurich.ibm.com>
Signed-off-by: Panos Vagenas <pva@zurich.ibm.com>
vagenas
changed the title
Signed-off-by: Panos Vagenas <pva@zurich.ibm.com>
cau-git
approved these changes
Oct 30, 2026
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
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.
A release broke tests that would break again at every release (186 tests for 0.9), for two reasons. This makes the tests survive a release unchanged.
from_next.pyandto_next.pyare renamed to the numbered steps (e.g.v0_9_to_0_8.py) and replaced by empty ones, so tests importing them by their development names lost their rules.utils/rotate_migration_steps.pynow also retargets the tests importing a development step (from doclang.migration._steps import to_next) to the released step. Other mentions, e.g. of the step files by name, are left alone. New test intests/test_prepare_release.py.tests/test_migration.pyandtests/test_validation.pytook 0.8 as the newest released version and 0.9 as the head. They now compute the newest released version and the next one.Checked by simulating the 0.9.0 release (version sync, step rotation, schema snapshot) on this branch: all tests pass, with the 6 skips expected right after a release.