Best Java Testing Articles during Summer 2011
Posted by Patroklos Papapetrou on August 31, 2011
Starting from today I will try to post every month or so , a list of articles that cover a specific topic and were initially posted during the last month.
For the beginning I the selected topic is Testing and covers not only August but also July. Enjoy!!
5 reasons to write tests for you code
If you are not yet convinced about the necessity of testing your code then this article is your last chance 🙂
Unit Testing for Java EE
Think testing Java EE applications is difficult, inconvenient, or too complex? Learn why this isn’t the case and how do unit testing efficiently in this article.Unit testing and mocking of Java EE 6 (CDI, JPA and EJB) applications.
Why testing code for thread safety is flawed
A blog for testing thread-safety code and the problems behind that.
Test Driven: It is the mindset not the tool!
Interersting point of view on how you have to approach TDD.
DBUnit Express Tips – Setup Simplification and Custom Data File Convention
Simple Guide for DBUnit Express. If you plan to perform Database Unit testing then drop an eye on this post
Good Unit Test Check List
Are you writing Unit Tests? Then check this list if you are on the correct path.
Unit Tests are better than excellent specification
Excellent specifications = Very refined exhaustive view of future potential features
Good unit tests = Very refined exhaustive view of actual features
What is the cost of Unit Tests
Simple blog showing how much you earn by writing unit tests instead of running manual tests or debugging your application
UDIAS – The five levels of an ideal agile testing strategy
The UDIAS (unit, database, integration, acceptance, stress) testing strategy is probably not a silver bullet, but it covers all the different layers and views of an application. The time needed to set running all the above build jobs is significantly large but the ROI of investment worth the effort. I don’t think that there is something more important in a system under development / maintenance than an automated testing plan.