Acceptance Tests, BDD & GO
summary
Argues that BDD reduces wasted rework by driving concrete examples into executable specs and shows a working Go workflow: write a failing acceptance spec with t.Run, implement a minimal HTTP endpoint /greet/{name} that returns a hardcoded "Hello, Ria!" to get green, then refactor the behavior into a domain package backed by unit tests. Demonstrates decoupling via an interface-driven driver pattern and running the same spec against containers using testcontainers for fast local and live verification.
AI-written summary · about
chapters (20)
- 0:00Start
- 0:03Bdd Acceptance Tests
- 0:35Intro
- 3:07What Exactly Is a High Performing Team
- 4:39Acceptance Tests
- 11:26User Story
- 12:00Concrete Examples
- 19:15Pitfalls
- 26:15Failing Acceptance Test
- 27:48Test Containers
- 32:26Domain Logic
- 34:18Additional Behavior
- 34:45Applying the Principles of Bdd To Go
- 35:01Writing a Test
- 36:43Failing To Write the Test First
- 45:32Database Testing
- 47:49Where Do You Keep Your Bdd Tests
- 49:12Writing the Failing Acceptance Test
- 50:44Is It Okay To Change the Acceptance Test
- 51:50Setup Data
related talks
48mBDD - It’s More Than Acceptance Tests
28mIntro to Test-Driven Development in Go
15mIntro to TDD and BDD
09m"Effective ways of using BDD concept for Testing"
01h 19mBDD and Acceptance Testing with RSpec & Capybara
34mAdvanced Testing Techniques in Go
40mMaking BDD Work for you
23mBDD To The Bone: Acceptance Testing with Behave and Selenium