Monday, November 21, 2011
Naming and organization is critical in keeping software systems maintainable as you move forward, especially with larger systems or systems with longer lifespans. You’ll find yourself spending large amounts of time stumbling around unclear, tangled source code if you don’t take care with how you lay out your classes, namespaces, and projects.
We should take the same exact care with our tests as the systems we’re delivering to our customers, because test code IS production code.
Careful naming and layout of your tests is every bit as important as the system itself—and perhaps even a bit more since we ...