This video demonstrates an example of agile requirements traceability. We discuss an example user story and show how detailed requirements captured as test tables can be used to build executable specifications and aid the design process. Finally we wrap up by a brief example of how we would track the …
Ruby’s testing culture goes way back, and has been a force for making many Ruby projects a showcase for solid, maintainable code. That said, within a business an exclusive focus on TDD and BDD can easily miss the bigger picture and drive optimizations in the development process that negatively impact …
Gospecify is a behavior-driven development (BDD) framework for Go. Rather than focus on testing every nook and cranny of some code, it helps a programmer produce an executable specification of that code’s behavior. Go’s syntax allowed gospecify to be almost as expressive as Ruby’s rpsec; however, a few tricks had …
Pickle adds many convenient Cucumber steps for generating models. Also learn about table diffs in this episode. Cucumber lets software development teams describe how software should behave in plain text. The text is written in a business-readable domain-specific language and serves as documentation, automated tests and development-aid – all rolled …
Ronica Roth briefly explains how to write good user stories. [youtube DaqyLWOEObY]
Quality Attributes (Non-functional requirements) as first class citizens of a project? Too far fetched? Len Bass, co-author of Software Architecture in Practice and longstanding member of the Software Engineering Institute (SEI), thinks he has an answer. But how does this fit in an agile world?
