I found Open source projects with good quality tests but I wanted to ask something a bit different.
I'm having a hard time visualizing how to build production code using TDD practices, particularly for networked database-driven applications where big chunks of functionality are dependent on开发者_运维知识库 one or more external systems. The two main strategies I've seen discussed for accomplishing that are decoupling code from the systems in question and using mocks. However, my intuition is that doing either one properly would also be complex and error-prone.
I'd like to take a look at some real-life code that was built using test-driven development practices from the ground up. Such a project would have had to deal with such issues from very early on, and I think looking at the results would be instructive. Any examples out there, whether positive or negative?
Some testing frameworks come to mind ...
- JUnit
- FitNesse
- RSpec (Though of course this was BDD rather than TDD!)
Both the Ioke and Seph programming languages, as well as their implementations ikj (Ioke interpreter for the JVM), ikc (Ioke interpreter for the CLI) and whatever the Seph implementations is called, and their standard libraries were written 100% test-driven or rather behavior-driven.
Since Autofixture was created to facilitate TDD, I'm sure that the source code for the project itself was developed according.
精彩评论