Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WORLDSERVICE-649 Rename cypress test file #12600

Merged
merged 18 commits into from
Apr 8, 2025
Merged

Conversation

emilysaffron
Copy link
Contributor

@emilysaffron emilysaffron commented Apr 3, 2025

Resolves JIRA: WORLDSERVICE-649

Summary

rename test file ws-nextjs-app/cypress/e2e/specialFeatures/liteSiteWeight/index.js -> ws-nextjs-app/cypress/e2e/specialFeatures/liteSiteWeight/index.cy.ts so it can run

also adds some new logging for the cypress test

Code changes

  • A bullet point list of key code changes that have been made.

Developer Checklist

  • UX
    • UX Criteria met (visual UX & screenreader UX)
  • Accessibility
    • Accessibility Acceptance Criteria met
    • Accessibility swarm completed
    • Component Health updated
    • P1 accessibility bugs resolved
    • P2/P3 accessibility bugs planned (if not resolved)
  • Security
    • Security issues addressed
    • Threat Model updated
  • Documentation
    • Docs updated (runbook, READMEs)
  • Testing
    • Feature tested on relevant environments
  • Comms
    • Relevant parties notified of changes

Testing

  • Manual Testing required?
    • Local (Ready-For-Test, Local)
    • Test (Ready-For-Test, Test)
    • Preview (Ready-For-Test, Preview)
    • Live (Ready-For-Test, Live)
  • Manual Testing complete?
    • Local
    • Test
    • Preview
    • Live

Additional Testing Steps

  1. List the steps required to test this PR.

Useful Links

@emilysaffron emilysaffron self-assigned this Apr 3, 2025
@emilysaffron emilysaffron changed the title Rename cypress test file WORLDSERVICE-649 Rename cypress test file Apr 3, 2025
// eslint-disable-next-line cypress/unsafe-to-chain-command
return cy
.wrap(requests)
.each(({ url, contentLength }) => {
if (contentLength) {
requestSizes.push({ url, size: contentLength });
Copy link
Contributor

Choose a reason for hiding this comment

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

Weirdly not seeing the ATI requests listed in the output (I was getting them locally when we first did the curl / content-length stuff...)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeaaa , it might be a timing thing? as those are fired off after the page load, so maybe they're not getting fired off fast enough to be captured in the requests sometimes - think maube this is fine as they're not technically part of the inital data a user has to download?

@emilysaffron emilysaffron merged commit b22bf33 into latest Apr 8, 2025
11 checks passed
@emilysaffron emilysaffron deleted the fix-cypress-test branch April 8, 2025 08:44
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.

3 participants