In my experience, I've found that many people and companies conflate and/or confuse TDD with unit testing in general. If someone asks me if I do TDD, I say no and then quickly explain that I'm less interested in when the tests are written - as long as they are written.
I've worked with a few people who always write the tests first. But the vast majority (90%+) tend to write tests during or after their code (or not at all!)
Totally agree. I also think "TDD" is often used to mean "Unit tests". Saying that you never unit tested your code during a job interview sounds a bit like suicide to me. On the other hand, I think no one will think it's a real problem if you code first and then unit test it.
Yeah, I also think that when most companies mention TDD they mean unit testing. In my current job I have practically zero at all to write tests as the main focus of the superiors is to get the most amount of results in the least amount of time possible...
We’re a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.