Skip to content

test(spp_registry): hold the phone-fallback and unlink-permission tests on a full stack (#443) - #541

Open
gonzalesedwin1123 wants to merge 2 commits into
19.0from
fix-443-registry-stack-tests
Open

gonzalesedwin1123 wants to merge 2 commits into
19.0from
fix-443-registry-stack-tests

Conversation

@gonzalesedwin1123

Copy link
Copy Markdown
Member

Part of #443 (weekly ci-full red). Test-only; the original two tests this issue was filed for, plus the one test red in all three stacks.

Causes

Evidence

  • Stack run -i spp_registry,spp_base_common,spp_starter_sp_mis on the two classes: 0 failed, 0 error(s) of 10 tests (both classes were red in the 2026-09-20 weekly run).
  • Module suite: 0 failed, 0 error(s) of 285 tests. All pre-commit hooks pass.

spp_registry 19.0.2.2.4 → 19.0.2.2.7 (2.2.5 and 2.2.6 are held by the unmerged #522 and #533; whichever lands out of order renumbers). README/index.html left for CI's generator.

…ts on a full stack

The unparseable-phone test builds its record with new() instead of
create(): spp_base_common, installed on every full stack, overrides
create() to refuse a number containing letters before the registry
compute is reached, so the test failed in all three demo stacks while
pinning behaviour every real deployment replaces on purpose.

The unlink-permission tests pin the starter bundles' admin-only registry
switch off for their transaction. spp_starter_sp_mis ships it on and
#411 enforces it server-side, so the manager the registry rule allows
was refused under the SP-MIS stack. The guard reads the parameter live
and the change rolls back with the test, as spp_mis_demo_v2's own
access-control tests already do.

Refs #443
@codecov

codecov Bot commented Sep 21, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 76.88%. Comparing base (1a3c591) to head (c8fd5ee).

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             19.0     #541      +/-   ##
==========================================
- Coverage   76.91%   76.88%   -0.03%     
==========================================
  Files         704      740      +36     
  Lines       45774    48024    +2250     
==========================================
+ Hits        35205    36923    +1718     
- Misses      10569    11101     +532     
Flag Coverage Δ
spp_analytics 93.25% <ø> (ø)
spp_api_v2 79.99% <ø> (ø)
spp_api_v2_change_request 73.37% <ø> (ø)
spp_api_v2_cycles 71.03% <ø> (ø)
spp_api_v2_data 77.77% <ø> (ø)
spp_api_v2_entitlements 70.23% <ø> (ø)
spp_api_v2_gis 74.60% <ø> (ø)
spp_api_v2_products 65.86% <ø> (ø)
spp_api_v2_programs 92.22% <ø> (ø)
spp_api_v2_service_points 71.03% <ø> (ø)
spp_api_v2_simulation 71.19% <ø> (ø)
spp_api_v2_vocabulary 57.75% <ø> (?)
spp_approval 50.85% <ø> (ø)
spp_area 80.16% <ø> (?)
spp_area_hdx 81.60% <ø> (?)
spp_audit 72.13% <ø> (?)
spp_base_common 91.07% <ø> (ø)
spp_programs 67.58% <ø> (ø)
spp_registry 89.00% <ø> (ø)
spp_security 69.56% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 36 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@gonzalesedwin1123

Copy link
Copy Markdown
Member Author

Full-stack evidence: SP-MIS ci-full dispatched on this branch (run 35565271638, at 54015f9) vs the 2026-09-20 weekly baseline (run 35499069639).

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.

1 participant