Extending GitHub Flow with Practical Testing
summary
Describes a concrete workflow that ties GitHub Flow to continuous integration and testing: pull requests gate builds and code review, git hooks plus a PR template with acceptance checks enforce the process, and CI tools (Jenkins, Travis, CircleCI) run unit, functional and long Selenium suites while Rainforest handles large browser matrices. Gives outcomes and constraints: teams reached about 97% code coverage and accepted ~40‑minute regression runs, adopted Amazon‑style rapid deploys and hotfixes from master, and found Jenkins requires extra memory at scale but the pipeline enabled small, frequent releases and team compliance.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 11:43Git Flow limits
- 16:24Testing in Git Flow
- 23:18Code automation
- 29:12Advanced Git tools
- 33:06Summary
- 36:37Q&A
related talks
39mRemove your Testing Bottleneck with CI/CD Pipelines
48mEnd to End DevOps with GitHub
32mContinuous Integration and Deployment: Five Lessons Learned
36mUsing Jenkins to Build, Deploy, and Automate Projects
26mAccelerating cloud native deployment with GitHub Actions and AWS
37mGitHub Actions + K8S to level up software dev
18mDeveloper Workflow Automation with GitHub Actions (CI/CD)
30mSpend More Time Coding & Automate the Boring Stuff