Making pgweb rock-solid: Using the Testing Harness to ensure the quality of pgweb
summary
An automated testing harness for the Official PostgreSQL website runs in a separate repo under GitHub Actions and monitors pgweb commits every six hours, kicking off Selenium functional tests plus a site-wide accessibility scan using Unlight housee accessibility. It uses Django test classes, a headless browser, and the Palm API to summarize failures, saves artifacts (currently 90 days) and can test arbitrary commit IDs. The documentation pipeline test goes from 20+ hours to 5 minutes, produces bug reports and archives results for follow up.
AI-written summary · about
chapters (10)
- 0:00Introduction and background
- 1:08What is PG web and why test it
- 5:04Introducing the testing harness
- 8:12How the harness works
- 10:16Functional testing explained
- 13:08Testing documentation pipeline
- 16:36Accessibility testing approach
- 19:47Current results and future plans
- 22:15How you can contribute
- 23:22Q&A session
related talks
36mAutomated Performance Testing of Postgres
30mFollow the Postgres brick road: a journey of testing against a real database server
01h 45mHands-On Web App Test Automation
27mQuality Assurance in PostgreSQL
40mAutomated Performance Testing In Preproduction
14mAutomated Visual Regression and Accessibility Testing Made Easy
01h 53mHands-On Web UI Testing
34mENABLING CONTINUOUS DEPLOYMENT OF PIXEL-PERFECT USER INTERFACES