Good Article : Write Right Java Faster Using Test-Driven Development

Write Right Java Faster Using Test-Driven Development

Testing Java code is increasingly a task taken on by developers rather than separate teams to which the programs are handed. Many Java developers are now familiar with JUnit and know the different between unit tests and integration tests. This has been driven largely by the focus on test-driven development (TDD) in extreme programming (XP) and other agile software development methodologies. While the industry-at-large has recognized the value of unit tests and has a new outlook on testing in general, for the most part, actual TDD (meaning, the tests are written first) is not usually practiced outside of hardcore agile shops.

In this article, we'll present a specific example (based on a real-world scenario that we recently faced) and walk step-by-step how to take a pure TDD approach and hopefully show the benefits of embracing TDD completely in this scenario. (For a clear and concise explanation of some of the major benefits of TDD in general, see www.extremeprogramming.org/rules/testfirst.html.)

The Scenario
This scenario is modeled closely on one we faced at a client site recently. In short, we were a pair on a development team working on a project with typical issues:

  1. A deadline/delivery date had been set
  2. Little or no requirements existed and
  3. It didn't look like we'd be getting requirements any time soon (due to limited staffing, etc.).

Read more.....

Comments

Anonymous said…
It's not my first time to visit this web site, i am visiting this web site dailly and take pleasant information from here everyday.

Here is my website: on line reputation management

Popular posts from this blog

Enabling high availability in Spring applications

Getting Screenshots in symbian phones

Good Article : About JSF & Struts [The add-and-remove pattern]