In this series we’ve already discussed the basics of TDD by creating our first test and then making that test pass. Last time I discussed the SOLID principles and how they help us in our practice of TDD. This time we’ll put two of the SOLID principles into practical application by discussing Dependency Injection.
Greetings, Testers. Peter and I have been thinking, talking and writing these past few weeks about changes we've seen over the past few years in the application development and testing field. I suspect that the most visible change to computing and applications — the one that, if you asked the average person on the street they would be most likely to mention — is the rise of mobile computing. The numbers vary between analysts, but I've seen reports estimating that somewhere on the order of 500 million smartphones[i] will have been shipped by the end of next year and ...
In the past we’ve taken great pride in the new and exciting features we’ve added to our JustCode product. Be it the ability to run JavaScript unit tests in the same test runner as your C# and VB.Net code or the ability to debug decompiled code right in Visual Studio, the team has made pushing the envelope and delivering great innovative features a habit. And more great stuff is on the way!
As promised some time ago, here is a post that explains the basics of working with the Global Assembly Cache (GAC) – what it is, pros and cons, how to recognize a GAC reference when you see it and how to add a new one.
Over the last few months, we’ve been working hard to deliver you an awesome Q3 2013 release (which you can read more about, here). Along the way, we figured today was good time to drop a Service Pack for Q2 2013, which includes a bunch of new features and a boatload of fixes. In this blog post, I’ll highlight a few of things we’ve added in this release.
Yesterday I wrote about things testers can learn from developers. Today I’d like to cover the flipside of that picture: what developers can learn from testers. Yes, there’s a significant amount of knowledge that can flow the other way, too! Developers can learn many things from testers that will help the team be more productive and ship better value to the customers. Unfortunately, devs will have to get past some stereotypes about testers. Too often testers get viewed as the angry, overly critical people who lose sight of important aspects of a project. Like focusing on shipping versus endless ...
In the previous two posts we started our practice of TDD with a simple example of a requirement, a couple of test cases and tests to match. We implemented the code necessary to make those tests pass. Along the way we discussed some of the tools we’ll be using going forward, including NUnit and JustCode. In this post I’ll be discussing the SOLID principals and how they can help with your practice of TDD and help you write better software in general.
Prioritized and Sized Backlog For agile planning to work, you must have a prioritized and sized (estimated) backlog. A prioritized backlog is simply a list of work that needs to get done that is ordered by priority. Essentially, the work at the top of the list is the most important and should be done first. In many cases, customers have a difficult time prioritizing lists of features, however, this makes the prioritized backlog even more important to produce. Another requirement of this backlog is that each of the items must be sized, which is another way of saying that the ...