The deeper I got into TDD, the more I felt that my own journey had been less of a wax-on, wax-off process of gradual mastery than a series of blind alleys. I remember thinking “If only someone had told me that!” far more often than I thought “Wow, a door has opened.” I decided it must be possible to present TDD in a way that gets straight to the good stuff and avoids all the pitfalls. My response is behaviour-driven development (BDD). It has evolved out of established agile practices and is designed to make them more accessible and effective for teams new to agile software delivery. Over time, BDD has grown to encompass the wider picture of agile analysis and automated acceptance testing.
Whether you are new to Windows Communication Foundation (WCF) or have worked with it a bit, there are some testing techniques and principles that will make your WCF work easier. There are several ways to think about what WCF is—I tend to think of WCF services as a major extension of Web services. Like Web services, WCF services allow you to create distributed systems using a service-oriented architecture. However, WCF services provide much greater flexibility (such as choice of transport protocol) and additional features (such as transactions and security). WCF is much more than merely an extension of Web services, but if you are new to WCF, initially thinking about WCF services in this way is a reasonable approach.
iOS developers generally don’t unit test. So why then do they as a community seem to enjoy a reputation for quality? No unit tests. No continuous integration. No TDD. That pretty much summarizes my last project. It was my first paying iOS gig, and not only did we not apply these cherished practices, we shipped a high quality product.
This guide will show you how to setup J2MEUnit in a modern IDE like Eclipse and write your first test case. Once you have followed all the steps you will have a test-driven development environment ready to go.
So, you've written a bunch of unit tests. As a developer, you run your tests multiple times per day, especially in a continuous integration environment. But how badly would they break if the sources had to change? When Jester and Maven combine to make Grester, you can quickly find out.