Front End Testing with GitHub Actions
summary
CI pipeline builds a preview site with GitHub Actions, deploys to Netlify deploy preview, captures the preview URL, and runs Lighthouse CI and Playwright against it, uploading reports as artifacts. A custom bash script wraps the Netlify CLI and outputs the URL as a job output; GitHub masks outputs that match secrets so the URL must be base64 encoded (the presenter used a base64 encode twice workaround) and decoded in the test job — the workflow then succeeds.
AI-written summary · about
chapters (10)
- 0:00Front end testing with GitHub Actions
- 3:17Why use GitHub Actions
- 6:27Understanding workflows
- 10:22Setting up build job
- 16:06Deploying test website
- 22:57Running automated tests
- 33:49Building production code
- 36:07Advanced use cases
- 42:55Resources and learning
- 43:16Q&A on security
related talks
47mFront End Testing with GitHub Actions
52mFront End Testing with GitHub Actions
18mAutomating All the Code & Testing Things with GitHub Actions
18mDeveloper Workflow Automation with GitHub Actions (CI/CD)
44mCI/CD with GitHub Actions
50m360° automation with GitHub Actions
31mGetting Started with CI/CD using Github Actions
01h 00mCI/CD and beyond with GitHub Actions