Using Behat as a Webapp Automation Tool
summary
Shows a practical pipeline that uses Behat + RunDeck to automate admin actions on 80 legacy Drupal sites: examples include resave themes on 80 sites after DB sync, run update.php, invoke a custom menu path that truncates cache tables, and change admin passwords. It uses PHP-based Behat step definitions, RunDeck secure options for credentials, a headless (no-JS) driver so updates require timeouts or polling, and returns pass/fail to RunDeck for alerting.
AI-written summary · about
chapters (13)
- 0:00Introduction to Behat
- 3:19Why we needed automation
- 7:23Behat basics and benefits
- 11:18Behat directory structure
- 16:52RunDeck integration demo
- 19:29Example 1: Resaving themes
- 24:06Example 2: Module updates
- 27:04Example 3: Cache clearing
- 29:14Example 4: Password changes
- 32:45Next steps and improvements
- 34:53Community contribution day
- 35:56Contact information
- 36:17Q&A session
related talks
49mBending Behat's Benefits: A live coding adventure
27mAutomated Web Acceptance Testing with Behat
34mTesting APIs written in PHP using the Behat feature testing tool
26mBehaviour Driven Development with Laravel
45mBehat from 0 to Hero: a Practical Guide
45mBehaviour Driven Development and Behat: Telling Stories Through Code
45mBehat for characterisation on tests
46mTest Your Drupal Site The Easy Way: Use Cypress
