Repository navigation
Conversation
A full coverage tag whose line ends with a comma after a covered ID now
continues on the following lines. Leading whitespace and punctuation
comment markers (e.g. "--", "//", "#") are ignored on continuation lines,
so covered IDs can be aligned:
-- [SRC~ICM45686-CORE~1->CPR~ICM45686-0001~1,
-- CPR~ICM45686-0002~1]
The joined tag is imported like a single-line tag located at the opening
line, with source ranges of covered IDs pointing to their actual lines.
An invalid continuation line or a missing closing bracket fails the
import instead of silently dropping coverage.
Only the Tag importer enables multi-line tags; Markdown, RST and Gherkin
comments keep single-line tags.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
The Gherkin importer now uses the multi-line coverage-tag parser for its
comment lines, so tests in .feature files can cover several requirements
with an aligned list:
# [TST~ICM45686-CORE-TEST~1 -> CPR~ICM45686-0001~1,
# CPR~ICM45686-0002~1]
Executable and blank lines are still never scanned for coverage tags.
If such a line interrupts an open multi-line tag, the import fails with
the file and line instead of continuing the tag across Gherkin text.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
ezwiebel
force-pushed
the
feature/632_multi_line_coverage_tags
branch
from
October 14, 2026 14:06
5a46ef0 to
5132d6d
Compare
Contributor
Author
|
I don't understand why the link checker fails. The link in trouble does lead to the correct page. |
This branch has not been deployed
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.
This PR is the implementation proposed for feature request #632.
It allows a user to write coverage tags on multiple lines in source code and Gherkin comments.
Specification, code, tests and usage documentation has been update with the assistance of AI.
The produced artifacts have been human reviewed and very slightly modified.
Attention points for reviewer:
Don't hesitate to come back to me anytime.
Coded with the help of Claude Code (sonnet 5.5 and opus 5.5), following the provided guidelines.