Repository navigation
MOSIP-45746: Bump apitest-commons to 1.8.0 and add coverage matrix - #609
Open
mohanachandran-s wants to merge 2 commits into
Open
mohanachandran-s wants to merge 2 commits into
mohanachandran-s wants to merge 2 commits into
Conversation
…e matrix - api-test/pom.xml: apitest-commons 1.7.0-SNAPSHOT -> 1.8.0-SNAPSHOT - api-test/src/main/resources/coverage/: CoverageCli init + 56 matrix files (4 wired subjects, 52 planned endpoints), 683 rows; 244/244 legacy Excel IDs in legacy-ids.txt; scenario flows F1-F18; README auth section; check-baseline.txt with 2 reasoned entries - .github/workflows/coverage-matrix-check.yml: CI caller for the shared coverage-matrix check CoverageCli check --fail-on-warnings: 0 gaps. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Mohanachandran S <mohanachandran.s@technoforte.co.in>
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
…efresh module docs The reusable coverage workflow is moving out of mosip-functional-tests (a library repo) into mosip/kattu. The caller now targets mosip/kattu and runs only on manual dispatch until that workflow exists. AGENTS.md and the README tooling section are re-rendered from the module-neutral commons templates; Summary.md is regenerated. Depends on mosip/mosip-functional-tests#2016. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Mohanachandran S <mohanachandran.s@technoforte.co.in>
lsivanand
approved these changes
Nov 13, 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.
Jira: MOSIP-45746
Changes
api-test/pom.xml: apitest-commons1.7.0-SNAPSHOT->1.8.0-SNAPSHOT.api-test/src/main/resources/coverage/: coverage matrix bootstrapped withCoverageCli init.legacy-ids.txt: all 244 test cases from the retired Keymanager TC Excel sheet, each mapped to a row..github/workflows/coverage-matrix-check.yml: CI caller for the shared coverage-matrix check. It points atmosip/kattuand is disabled (manual dispatch only) until that reusable workflow exists; a kattu PR will follow when the check is enabled.No YAML, templates, suite XML or Java changed.
Verification
CoverageCli check --fail-on-warnings: 0 gaps. 2 possible-duplicate rows are baselined, each with a reason. A secondsyncwrites nothing.Known issues (please read)
KER-KMS-002(ApplicationId not found in Key Policy), even though the key-policy DB setup logged success in both runs. The root cause is not confirmed. These failures were accepted by the task owner to unblock this PR and need follow-up before relying on 1.8.0. The other 2 failures (GenerateCSR_02, _04) already fail on base.Summary.mdhere are rendered from that PR's module-neutral templates, so merge #2016 first; runningsync/checkagainst older commons regenerates the old text and reportsreports-stale. The coverage CI check stays disabled until the kattu workflow exists, so runCoverageCli checklocally meanwhile.⚠️ Possible bugnotes with file:line. Some planned rows expect the product behaviour (for example 401KER-ATH-401with no token), so they fail against today's service by design. No defects have been filed.🤖 Generated with Claude Code