Implement automated browser testing

[coredoesdev]

Description
Large upgrades/refactors like spatie/html or Bootstrap 5 are difficult to QA due to the large amount of code covered. Implement automated browser testing with something like Playwright (https://playwright.dev) to ease the burden of testing for these large PRs.

Acceptance Criteria

• Implement Laravel Dusk automated browser testing
• Add tests covering all code paths on the site
• Ensure all tests pass
• Add a GitHub Actions check to verify all tests pass in CI
• Ways of Working: Update to enforce adding tests on all new features. We should aim for 100% coverage if possible

Accepted By:

Dev Notes
https://playwright.dev
Consider Laravel Dusk as an option https://laravel.com/docs/11.x/dusk
https://codecourse.com/articles/running-laravel-dusk-on-github-actions
Depends on the Vite migration and several other PRs, listed below. Do not start work until these other PRs are merged:

• Migrate from mix to vite #444
• #414 Upgrade site to Laravel 11 baseline #566
• #562 Update html form builder #565
• Migrate site to bootstrap 5.3.x #386

XD Notes

Working Branch
Browser-testing

PR
#666

Feature Toggle

QA Notes

• QA on local only... do not attempt on one of the live environments
• Run: php artisan dusk:chrome-driver to install the chrome driver, then
• Run: php artisan dusk
• If Create training team feedback system #646 has not been merged, you will have 1 error due to a missing route

Deployment Notes