dootdoot

unless you use a dynamic language :P

That makes sense. I've found automated testing to be incredibly useful and just necessary to be able to really rework code well. Not using automated testing and having a really fast release cycle seems like a recipe for a lot of pain (and they said that testing was taking them forever).

I asked them about their testing - turns out they were looking to have someone help them develop a way to test their software (so at least they want to do it).

I wish I'd asked them the two questions you listed at the end, they are much better questions than a bland "do you test?". They did break the build some times.

as the actual OP, I can definitely say I wasn't talking about TDD. I mean integration tests like "Hey, we aren't double charging this person" or tests to make sure that bugs stay fixed. It doesn't matter to me if you write tests before or after the fact, you just should be testing so you can have some sort of sense of correctness.

Yeah, it's not about TDD, it's about having your testing be a non-automated checklist (without unit tests where useful)

There's an existing project for GitHub called Hub. Why did you pick a name that overlaps with it?? https://github.com/github/hub