@robb1e Software Engineer, Pivotal Labs Robbie Clutton Quarantine 

@robb1e $ rake ..........F......... $ rake ................... $ rake ....F...........F.... $ rake ................... 

@robb1e You say... Oh, it’s just that flakey test, run the build again 

@robb1e 3 minutes ago: failed 12 minutes ago: passed 30 minutes ago: failed 45 minutes ago: failed 2 hours ago: passed 

@robb1e You say... Run all build agents, one of them will go through 

@robb1e 

@robb1e Confidence, meet window 

@robb1e @quarantine Scenario: Something flakey #.... describe “Flakey”, :quarantine do # ... 

@robb1e #regular ci build #!/bin/bash cucumber --tags ~@quarantine rspec . --tags ~quarantine 

@robb1e #quarantine ci build #!/bin/bash cucumber --tags @quarantine rspec . --tags quarantine 

@robb1e Regular Quarantine Deploy Continuous Integration 

@robb1e BUILD NANNY 1. Rewrite 2. Rethink 3. Delete 

“You should not be afraid to delete tests that are no longer providing value, no matter whether you originally planned to keep them or not. We tend to treat tests as these holy creatures that live blameless, irreproachable lives once they have sprung into existence. Not so. The maintenance required to keep a test running weighs against its value in further development. Sometimes these lines cross, and the test simply becomes a burden on the project. Having the skill and experience to recognize a burdensome test is something we should be bringing to our clients, as well as the fortitude to rewrite it, rethink it, or delete it." - Adam Milligan 

@robb1e Request Controller Model View Javascript Decorator Database 

@robb1e $ rake ................... $ rake ................... $ rake ................... $ rake ................... 

@robb1e 3 minutes ago: passed 12 minutes ago: passed 30 minutes ago: passed 45 minutes ago: passed 2 hours ago: passed 

@robb1e Time to get the confidence back 

@robb1e Q/A