Screencast Catalog

In this episode Andrew and Brian cover the data structure behind git, what commits are really composed of, and how they think people should try and think when using Git. The hope is that this will help get people over one of the larger hurdles in the learning curve of Git.


In this episode Andrew and Brian cover the topic of Isolation tests, Integration tests, and how they relate to each other. They do so by using the example of a Smart Thermostat and looking at an Isolation test and an Integration test for that Smart Thermostat. After going through the examples they discuss the relationship of Isolation, Integration, State Based, and Behavioral tests using something they refer to as the axis of tests.


In this episode Brian and Andrew cover the concept of State Based Tests and the concept of Behavioral Tests. They discuss the differences between the two types of tests as well as some patterns to classify tests within these concepts. They do so by driving out a small example with TDD.


In this episode Brian and Andrew demo a recent open source tool Andrew built to assist with running Jasmine specs from the command-line or editors. Snapdragon packages Jasmine so getting up and running is as simple as installing the snapdragon gem and writing your first Jasmine spec. It also supports running a specific test or describe block by specifying the file/path:line_number. These among many other features make it an excellent tool improving developers workflows when they are BDDing out some JavaScript using Jasmine.


In this episode Brian and Andrew drive out the majority of the Signup Cucumber scenario that was outlined in Episode 5. This should help with understanding exactly how the BDD process is used by developers in their everday workflow. It shows the Red-Green-Refactor cycle being applied in an outside-in fashing starting at the Cucumber Scenario and driving all the way into very targeted RSpec Isolation tests.


This episode is an example of what it might look like for the Product Stakeholder and Technical Staff to flesh out a Cucumber Scenario. The first part of the covers Brian and Andrew's exploration of the product features driven by the task of writing the first Cucumber Scenario. This discussion helps them finalize on some questions around the intended target of the application and what the core feature set should consist of. The second portion of this episode covers the evolution of the first Cucumber Scenario for the project, User Signup, as Brian and Andrew iterate the scenario until they are happy with it.


This is the first episode in a mini-series where we will be using BDD to drive out a code snippet tracking tool called Snipster. In this episode we get the initial Rails skeleton for Snipster up and we also setup the necessary tools for BDD, Cucumber & RSpec. Beyond that we talk about different databases and setup up the database in our environment. This episode handles most of the setup to prepare us to really dive into writing code in the follow screencasts.


In this episode we reset the state of code to the point where in episode 2 we should have dropped down and fleshed out the RSpec tests for the controller. This episode covers the very basics of RSpec while we drive out a Rails controller action as part of the feature outlined in episode 2.


In this screencast I give a basic introduction to Cucumber. To explain Cucumber and how to use it I use a real-world example of adding the list screencasts feature to The Code Breakdown Rails app. I start out writing a Cucumber feature and explaining it and then dive into using that feature to drive out the implementation.


This is the first episode of The Code Breakdown. It covers BDD at a high-level. Explaining where BDD is pulled from, and some of the problems it solves. It also covers the core principles of BDD and the BDD test stack. Beyond that it goes into the BDD tools and an overview of the BDD cycle.