BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Unit Testing Content on InfoQ

  • Tackling real-world unit testing problems

    All the information, books and tools are out there, just pick up NUnit, and you’re good to go, right? Not exactly. Even before deciding to start unit testing, we need to sift through real experience of others; good and bad, horror stories and miracles (“This one test saved me a week of work!”). Then, we take the plunge, and realize: There’s so much to learn!

  • Testing SQL Server Code with TST

    Automated Testing (unit/integration) is an integral part of any agile development process. However a project with significant logic housed in database code creates severe constraints to writing unit level tests, especially if it is large, complex and depend on data. We will explore the TST framework and a few ideas for writing and maintaining good tests for database code.

  • First Steps in Unit Testing

    Unit testing goes hand in hand with other agile practices, so starting to write tests is a stepping-stone for organizations wanting to go agile. The road is long, but is worth taking. In this article, Gil Zilberfeld cover tips on what to expect, and steps to take when starting out in order to make unit testing a part of development life.

  • Writing a Comprehensive Unit Test

    A common theme amongst people professing “best practices” for unit tests is that you should only write a single assertion for each test. People who make these proclamations rarely show any unit test and those that do only show one. Yet this pattern may require a dozen other unit tests to ensure quality for even a trivial operation. This article uses examples to question that recommendation.

  • Design for Testability – The True Story

    Testing is a major activity in any development lifecycle - a large part of a project budget is spent on it. If we want to effectively use it, the ease of testing should be addressed from the early stages of building the system.

  • Virtual Panel: Specification by Example, Executable Specifications, Scenarios and Feature Injection

    In the last couple of years terms like Specification by Example, Executable Specifications and Feature Injection have showed up quite frequently in the community, often in relation to Behaviour Driven Development (BDD) or tools like Cucumber or SpecFlow. InfoQ have talked to some of the leading experts in this domain about what these practices are and how they relate to BDD.

  • Virtual Panel: State of the Art in JavaScript Unit Testing

    Unit testing is a commonly accepted practice in order to deliver maintainable code. This is especially true for a dynamic language like JavaScript and there are currently several frameworks and libraries for a team to choose from. InfoQ had a Q&A with the creators of some of the leading JavaScript unit testing frameworks about their projects and what they offer to developers.

  • Testing Misconceptions

    In this article Liam O'Connor explains some of the common misconceptions about testing. If you write your tests with these in mind, he hopes that it will help you and your team to decide when it is appropriate to test, and when it isn't.

  • Using Coding Katas, BDD and VS2010 Project Templates: Part 3

    This is the third and final part of the late Jamie Phillip’s exploration into the world of coding kata’s and Behavior Driven Design. This part shows how to incorporate VS 2010 project templates into the testing process.

  • Using Coding Katas, BDD and VS2010 Project Templates: Part 2

    This is the second of a three-part series on how Jamie Phillips used a combination of coding katas, behavior driven development, and project templates to improve his development practices. In this part Jamie introduces the reader to behavior driven development and explains how it can improve the effectiveness of unit testing.

  • Using Coding Katas, BDD and VS2010 Project Templates: Part 1

    This three-part series on using coding katas in practice Behavior Driven Development was written by the late Jamie Phillips, a well-known member of Boston's Agile and .NET communities. When we saw the first draft of this article we were all eager to publish it, but he passed away before we could finish the editing process. With the permission of wife Diana, we proudly present his final work.

  • Skills for Scrum Agile Teams

    The skills required to be hyper-productive in agile projects are different from those required by a traditional one. This article identifies behavioral and technical skills required for a team to have that edge. Anyone who acquires these "delta" traits should be equipped with the right set of behavioral and technical skills, which enable them to work effectively in an agile project.

BT