Skip to content

Conversation

@axlewin
Copy link
Contributor

@axlewin axlewin commented Nov 11, 2025

This shouldn't be merged until the corresponding API change has been in for a release cycle, and potentially not until some content uses the new stage.

The VRT changes are as expected; the mock concept page doesn't actually have an Advanced audience, this is just what we were previously using as a default.

Re-use the Scottish Higher colour to distinguish post-18 from core/advanced
@codecov
Copy link

codecov bot commented Nov 11, 2025

Codecov Report

❌ Patch coverage is 18.18182% with 9 lines in your changes missing coverage. Please review.
✅ Project coverage is 41.68%. Comparing base (c5c833e) to head (af04206).
⚠️ Report is 106 commits behind head on main.

Files with missing lines Patch % Lines
src/app/services/userViewingContext.ts 0.00% 5 Missing and 1 partial ⚠️
src/test/pages/Concept.cy.tsx 0.00% 2 Missing and 1 partial ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1827      +/-   ##
==========================================
- Coverage   41.73%   41.68%   -0.05%     
==========================================
  Files         542      542              
  Lines       23685    23688       +3     
  Branches     7855     7874      +19     
==========================================
- Hits         9884     9875       -9     
+ Misses      13757    13171     -586     
- Partials       44      642     +598     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Copy link
Contributor

@sjd210 sjd210 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. I'll merge the other parts in now and give this a week (with one small request that I might not have asked for ordinarily, but am since we're waiting anyway)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Arguably this Advanced context label shouldn't have even shown up in the first place, since "advanced" wasn't a labelled stage for the accordion section (and it's a content problem if "core" or "advanced" is not present, which it is in the vast majority of cases according to my searching).

That said, I think we should be testing this stage-label anyway. Could we either change the mock data so that it does include "advanced", or perhaps switch to "All exam boards" in the context switcher?

Copy link
Contributor Author

@axlewin axlewin Nov 12, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed, and agreed; I can't see why we should ever default to "advanced", but it would be nice to still test the labels somehow. I'll add "advanced" to the mock data.

(Edit: Changed to your second suggestion ("all exam boards") instead, to avoid needing separate mock contexts for each site)

@sjd210 sjd210 merged commit 2f0023a into main Nov 21, 2025
10 checks passed
@sjd210 sjd210 deleted the improvement/post-18-stage branch November 21, 2025 11:33
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.

4 participants