December Issue of NFJS, the Magazine published.
Here’s what is in this month’s NFJS, the Magazine
Brian Sletten – BDD and REST
Forward-looking development teams have started to use Behavior-Driven Development (BDD) in the past few years to test their code against clearly expressed acceptance criteria. The adoption of tools like Cucumber, JBehave, RSpec and EasyB show that this trend is growing. As we see an increase in the use of resource-oriented APIs, there is an opportunity to apply these testing ideas to make sure our services do what they are supposed to, maintain high quality and avoid accidental breakage.
Ken Kousen – Mocks and Stubs in Groovy Tests
True unit testing means isolating the class you’re testing from all of its dependencies. If the dependencies are simple, you can write your own stub classes and maintain them yourself. Java provides several mocking frameworks that allow you to set expectations and verify the interactions between your class and the mocks. If you have Groovy available, however, you have many capabilities built right into the language. This article will show you how to use Groovy to generate both mocks and stubs in an easy, controlled way.
John Griffin -Algorithms for Better Text Search Results
This article discusses four enhancements to searching: utilizing synonyms to broaden results, reducing search terms to their most basic form, fuzzy queries (there’s that word again) to help with misspellings and “did you mean?” suggestions, and finally, phonetic equivalents for search terms. We will be using code written in both Lucene and Hibernate Search format so some experience with these packages will be helpful but not absolutely necessary. Regardless of what your favorite language might be, these examples will give you ideas to use in your own code.
Brian Tarbox – Knowns and Unknowns of Scrum and Agile
One of the premises that Scrum operates from is that most interesting projects have constantly shifting requirements and exist largely in isolation from any previous implementation or design. Anyone mentioning static requirements or things we “know to be true” isn’t “agile”. This leads to missing the advantages gleaned from previous projects; which is odd given Scrum’s penchant for transparency and feedback. Scrum is great at responding to unknowns found during a sprint, but not so good at doing the same with facts from outside a sprint. As an overreaction to the Big Design Upfront paradigm, Scrum tends to view all projects as swimming in a sea of shifting requirements with little or nothing known upfront. It also tends to assert that we can succeed in spite of, or even because of, all of the variables facing a project. This paper asserts that this is a serious limitation of Scrum and shows what this limitation causes us to miss.
Here’s what is in next month’s NFJS, the Magazine
This is the last issue of the year. The magazine will return in March, 2012.
I’m very proud of the work we do on this new magazine. The staff and I have worked hard to produce a top-notch magazine that is unique in the realm of software development magazines. The magazine costs $50 per year, which includes 10 issues. Each issue has at least four articles. You can download in a print-quality PDF and two mobile formats: EPUB (for the Nook and iPad) and MOBI (for the Kindle). The articles are professionally edited and are written by top experts in their field, so the content is worth well more than the $50 you pay.
The June issue just published this morning and you can subscribe here: http://bit.ly/fETp6d. As always, if you have questions just comment on this post and I’ll respond quickly.