Why is test driven development missing from Joel’s Test?
I was reading this blog by Joel Spolsky about 12 steps to better code. The absence of Test Driven Development really surprised me. So I want to throw the question to the Gurus. Is TDD not really worth the effort?
Can I start with a passing unit test?
Uncle Bob’s rules for TDD are specified here.
Do I need to learn python first to understand the part 2 of the book Test Driven development?
It seems like Python is used as a coding language for part 2 of Kent Beck’s book Test Driven Development. I have read the first part of that book and started appreciating the value of TDD . First part was easy to understand as the examples were in Java and that is the only language that I have worked on. How should I prepare myself to go about reading the second part of the book? What value will it provide? I do not plan to write a testing framework myself. Can I skip this entirely and go to the third section?
Is there a modern replacement for a mutation testing tool like Jester for Java?
“Why just think your tests are good when you can know for sure?
Sometimes Jester tells me my tests are airtight, but sometimes the
changes it finds come as a bolt out of the blue. Highly recommended.” – Kent Beck
Should I use TDD and BDD if my project is changing fast?
I have my own little project I am creating using RoR, I plan it to have small-medium load.
With no doubt I started with BDD and TDD (Cucumber and RSpec to be exact, but I am also experienced with TestUnit), I like it but since it’s my own project and it’s a somewhat startup – I am changing many things in it, many requirements, many ideas how things should work and look. So it becomes too much time-consuming to always code it using BDD and TDD, even if I cover only common cases.
What should I do? Should I sacrifice BDD and TDD for productivity till I get to some point when I have a solid basis and it’s time for production, and than I write tests?
Should I write them right now but as minimal as possible? Should I only write RSpec and forget about Cucumber for now? Or maybe just TestUnit to test model for now since it’s the most important and everything else can change?
Thanks in advance!
What’s the next logical TDD move in this learning example?
I’m inching my way up the TDD ladder and I’ve got to a point where I’d like to get advice on the “next move”. I realize there might not be a single answer here, so any logical suggestion would be great.
In TDD, if I write a test case that passes without modifying production code, what does that mean?
These are Robert C. Martin’s rules for TDD:
Understanding unit tests/TDD for ASP.NET webforms [closed]
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for […]
How to time the sprints in Scrum to allocate time for TDD?
We have sprints of 4 weeks duration. What I have been doing is 3 weeks dev time and 1 week of pure manual/automated testing, stabilization and shipment assurance testing.
Why do we write our specs in different files from our source?
The D Programming Language supports writing unit tests inline with source. There’s a Ruby gem called test_inline that lets you write specs in the same file as your code.