Testing in Software Development Process: TDD And BDD
summary
Compares working practices: unit tests fail-first (TDD) for small components connected to an Oracle database using native language test libraries, plus executable BDD scenarios that formalize business acceptance. Tests run in CI overnight and produce daily pass/fail reports so regressions surface before deployment. Claims that TDD gives faster developer feedback on implementation gaps while BDD forces concrete business rules into reusable specifications, reducing ambiguity between banking product owners and developers.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 2:06What is TDD
- 7:20What is BDD
- 12:14TDD vs BDD differences
- 15:51Benefits of TDD
- 18:20Benefits of BDD
- 20:28Tools and methods in banking
- 23:08TDD demo walkthrough
- 25:40Running and reporting tests
- 29:07Test coverage and results
- 31:37Q&A
related talks
43mBDD vs TDD vs TDD vs TDD
15mIntro to TDD and BDD
31mBDD: Behaviour Driven Development
48mBDD - It’s More Than Acceptance Tests
47mTDD + BDD = TBD (Tests, Business, Development). A Triad of Engineering Culture
48mMake Your Life Simple and Carefree with BDD
58mTDD for database related code, how is it possible?
41mBDD Crash Course for Testers