Tutorials and resources on how to useTest-Driven Development (TDD) to apply Agile testing in software testing
Javascript becomes much more important to interactive website development then before (ok it has been for a while already) but the notion of testing that logic seems even further fetched then testing the code written in C#, Java. And this is something that is wrong as well.
System tests have the reputation of being slow (not entirely avoidable, I admit), difficult to automate reliably and difficult to diagnose when they fail. However, I find that many teams follow a TDD process at the unit-level, but do post-hoc testing at the system level, and so don’t use system tests as a source of design feedback. This blog post shows how you should do TDD at the system scale.
This book is primarily aimed at .NET developers interested in starting with TDD and those who already practice unit testing and want to move beyond that into development driven by acceptance testing.
Most developers think that the most beneficial part of using test-driven development (TDD) are the tests. But, when done right, TDD improves the overall design of your code. This installment in the Evolutionary architecture and emergent design series walks through an extended example showing how design can emerge from the concerns that float up from testing. Testing is only a side effect of TDD; the important part is how it changes your code for the better.
This video demonstrates the basic of Test Driven Development in Java using Eclipse. From basic tests and basic production code, to refactoring, and some splashes of Behavior Driven Development, watch production code get created test first.
The article “Writing Testable Code” presents practices to write more testable code with many examples in java, going a step further than just TDD.
Over the years I have come to describe Test Driven Development in terms of three simple rules.
Copyright © 2009-2024 Software Testing Magazine by Martinig & Associates