I started working on my first non-trivial application and having no test suite started hurting me within a few days. Inconsistencies between my local and Heroku environments just feel like whack-a-mole with no easy insights into where along the commit line they broke. `git push heroku` feels blind as I cross my fingers.

Now I'm in the process of applying tests retroactively which is even more painful. I'm doing this "retro-TDD" process of breaking my app and writing tests until they go green when I fix my app.

I suppose this is a necessary journey to actually practicing TDD.

No, sounds like he used PM [1].

1. http://programming-motherfucker.com/

hey danneu, Unfortunately no. The logic for the cucumber tests are written out, so if another coder took a look at the .features, they'd be able to figure out what the app needs to do. But as far as the tests working if I cmd 'cucumber'; they would all fail as they aren't defined yet.

The main reason for this was, me and Josh were actually going to only do Freelancify for a week or two without testing, then scrap it and re-do it again BDD test driven.

I ended up putting so much work into it in the weeks, that starting over from scratch would be a huge time-killer. One of the next things on the to-do is to go back and make these cucumber tests work.

Josh and I are probably also going to start on another small app so I can do BDD first, then code.