In a word, yes. It won’t be easy. You’ll need to learn new terminology. You’ll need to be patient. You’ll likely have to get a bunch of figures on your monitor. Why Collaborate? Why should testers and developers collaborate? It’s a perfectly legitimate question, particularly to those who’ve been in the software industry for a number of years and have seen the coming and going of any number of buzzword fads. Collaboration among members of a team producing software isn’t just a fad. The IT industry is finally moving away from stove piped, separated groups to a much healthier, more ...

In the last release we made some major improvements in TeamPulse so it can provide smoother experience on mobile devices. Now it’s even easier to track your work from your iPad or your smartphone. TeamPulse on your tablet We have done a lot of performance and UX improvements for mobile device. As a result you now got a faster board and list view, better search, quick add and activity stream, and more. While you would experience those for yourself, we wanted to share with you some tips and tricks on how to make your life easier when working with TeamPulse ...

In the previous post I discussed the tools I will be using in this series; Visual Studio 2013 Preview as my development environment, NUnit as my unit testing framework and JustCode as my test runner. I also introduced a requirement and wrote my first test to capture that basics of that requirement. In this post I’ll demonstrate one of the most important concepts about TDD by writing just enough code to make the first test pass. I’ll then add more tests to introduce more functionality to our library.

The importance of requirements Requirements are the lifeblood of the project.  I need to establish first and foremost. Good, detailed requirements will carry the project team through to the end of a successful project more times than not.  And that’s a good thing because more projects actually fail than succeed.  However, weak or incomplete requirements will not – resulting in countless hours of rework, scope creep that can drive any project manager crazy trying to manage and maintain control over, and the potential for many change orders that will upset the most satisfied project customer quickly making them wish they had never brought their project needs to you in ...

In this post I will introduce you to JustCode and the NUnit testing framework. I’ll also demonstrate the basic TDD workflow from introduction of the first requirement all the way through to writing your first test. At the end of this post you will have a test based on a given requirement. In the next post we will work through the rest of the workflow and make the test pass.