chore: Add Playwright tests scaffolding and initial tests

[lsr-explore]

Fixes

• Add playwright and playwright axe #563

Add Playwright test scaffolding and initial tests

Tests help prevent regressions and can identify accessibility issues.

What is in this PR

• Scaffolding for playwright
• Tests for PR # 536 raised for issue #536 - Bug: Blog Authors showing incorrectly
• Accessibility checks

Note

If the team decides to proceed with this change, the Playwright docs should be reviewed for what should be included in the playwright config file.

---

How to run playwright

run without the us

npm run test:e2e

---

run with the ui

npm run test:e2e:ui

---

References

Playwright

https://playwright.dev/
https://www.npmjs.com/package/playwright

@axe-core/playwright

https://www.npmjs.com/package/@axe-core/playwright

Astro docs - Testing

https://docs.astro.build/en/guides/testing/

[netlify]

✅ Deploy Preview for accessiblecommunity ready!

Name	Link
🔨 Latest commit	d864152
🔍 Latest deploy log	https://app.netlify.com/projects/accessiblecommunity/deploys/6a4fea5ea2de1100087b44f2
😎 Deploy Preview	https://deploy-preview-551--accessiblecommunity.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[brian-montgomery]

@lsr-explore : Were you running these inside of our Docker container? When I try to install playwright, I get the following error:

Playwright Host validation warning: 
╔══════════════════════════════════════════════════════╗
║ Host system is missing dependencies to run browsers. ║
║ Missing libraries:                                   ║
║     libglib-2.0.so.0                                 ║
║     libgobject-2.0.so.0                              ║
║     libnspr4.so                                      ║
║     libnss3.so                                       ║
║     libnssutil3.so                                   ║
║     libsmime3.so                                     ║
║     libgio-2.0.so.0                                  ║
║     libatk-1.0.so.0                                  ║
║     libatk-bridge-2.0.so.0                           ║
║     libdbus-1.so.3                                   ║
║     libcups.so.2                                     ║
║     libexpat.so.1                                    ║
║     libxcb.so.1                                      ║
║     libxkbcommon.so.0                                ║
║     libasound.so.2                                   ║
║     libgbm.so.1                                      ║
║     libX11.so.6                                      ║
║     libXext.so.6                                     ║
║     libcairo.so.2                                    ║
║     libpango-1.0.so.0                                ║
║     libXcomposite.so.1                               ║
║     libXdamage.so.1                                  ║
║     libXfixes.so.3                                   ║
║     libXrandr.so.2                                   ║
║     libatspi.so.0                                    ║
╚══════════════════════════════════════════════════════╝
    at validateDependenciesLinux (/website/astro/node_modules/playwright-core/lib/coreBundle.js:27624:9)
    at async Registry._validateHostRequirements (/website/astro/node_modules/playwright-core/lib/coreBundle.js:29051:18)
    at async Registry._validateHostRequirementsForExecutableIfNeeded (/website/astro/node_modules/playwright-core/lib/coreBundle.js:29173:11)
    at async Registry.validateHostRequirementsForExecutablesIfNeeded (/website/astro/node_modules/playwright-core/lib/coreBundle.js:29162:11)
    at async installBrowsers (/website/astro/node_modules/playwright-core/lib/coreBundle.js:67954:5)
    at async _Command.<anonymous> (/website/astro/node_modules/playwright-core/lib/coreBundle.js:69577:7)

There is a playwright docker container, but it doesn't seem like you used that?

[brian-montgomery]

Thanks, Laurie. This looks great. Thank you for converting it over to docker.

The easiest way we can fix the node_modules problem you note below is to mount a volume in docker for the node_modules and have them stored there. The downside is that the IDE must mount the docker volume to gain access to the packages installed there, which can be a pain.

I don't know how many people switch back and forth, so that may not be an issue.