Skip to content

fix: update entries taxonomy tests to use real stack data#351

Open
aniket-shikhare-cstk wants to merge 1 commit intodevelopmentfrom
fix/entries-taxonomy-test-data
Open

fix: update entries taxonomy tests to use real stack data#351
aniket-shikhare-cstk wants to merge 1 commit intodevelopmentfrom
fix/entries-taxonomy-test-data

Conversation

@aniket-shikhare-cstk
Copy link
Copy Markdown

Summary

  • Taxonomy tests in entries.spec.ts were failing on dev11 with errors.term.not_found (404)
  • Root cause: tests used placeholder taxonomy terms (taxonomies.one/term_one/term_one_child) that were unpublished or missing on the test stack
  • Updated all taxonomy references to use real, published data (taxonomies.usa/california/san_diago), consistent with taxonomy-query.spec.ts

What changed

  • Replaced hardcoded taxonomies.one/term_one/term_two with constants (TAX_FIELD, TAX_TERM, TAX_CHILD_TERM) using real USA taxonomy hierarchy
  • $or test now uses USA + India taxonomies instead of one + two
  • $and test simplified to use term equality + field existence on the same taxonomy
  • $eq_above and $above tests now correctly use san_diago (child term) for parent lookups
  • Removed defensive try-catch in $above test that masked the real failure

Test plan

  • All 18 tests in entries.spec.ts pass locally against dev11
  • Verify in GoCD pipeline against dev11

Taxonomy tests in entries.spec.ts were using placeholder terms
(taxonomies.one/term_one/term_one_child) that were unpublished or
missing on the test stack, causing $eq_below and $above queries to
fail with 404 errors.term.not_found.

Updated all taxonomy references to use real published data
(taxonomies.usa/california/san_diago) consistent with
taxonomy-query.spec.ts.
@aniket-shikhare-cstk aniket-shikhare-cstk requested a review from a team as a code owner April 9, 2026 15:53
@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 9, 2026

🔒 Security Scan Results

ℹ️ Note: Only vulnerabilities with available fixes (upgrades or patches) are counted toward thresholds.

Check Type Count (with fixes) Without fixes Threshold Result
🔴 Critical Severity 0 0 10 ✅ Passed
🟠 High Severity 1 0 25 ✅ Passed
🟡 Medium Severity 1 0 500 ✅ Passed
🔵 Low Severity 0 0 1000 ✅ Passed

⏱️ SLA Breach Summary

✅ No SLA breaches detected. All vulnerabilities are within acceptable time thresholds.

Severity Breaches (with fixes) Breaches (no fixes) SLA Threshold (with/no fixes) Status
🔴 Critical 0 0 15 / 30 days ✅ Passed
🟠 High 0 0 30 / 120 days ✅ Passed
🟡 Medium 0 0 90 / 365 days ✅ Passed
🔵 Low 0 0 180 / 365 days ✅ Passed

✅ BUILD PASSED - All security checks passed

@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 9, 2026

Coverage report

St.
Category Percentage Covered / Total
🟢 Statements 99.32% 877/883
🟢 Branches 97.23% 281/289
🟢 Functions 97.95% 191/195
🟢 Lines 99.4% 832/837

Test suite run success

654 tests passing in 31 suites.

Report generated by 🧪jest coverage report action from 3398d83

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.

2 participants