Test'em 'Scripts is a terminal-based test runner that makes cross browser Javascript unit testing easy.

As the product backlog is living and changing in time, in accordance with the new assessment of business value as discovered during latest market studies, the definition of done is a living object that has to be continuously adapted to the specific sprint and overall project goals.

We can all agree that shared responsibilities are important on a project, but we should also have clear accountability. Someone must ultimately be answerable for the correct and thorough completion of the deliverable, and that should be a unique individual.

If you want to introduce ATDD to a project or client, common sense says to begin by choosing the tool you want to use. This article quash that common-sense notion, because it doesn't work.

One of the biggest problems on many agile teams is forgetting the real business value of the feature they are developing. Even with all the testing done for each story, the team may deliver a feature that has outstanding issues, or does not meet the customer’s expectations. This article covers how to balance the fast feedback of working in small increments and iterations with ensuring that the overall feature delivers adequate business value.

PyInq is a Python unit testing framework created in the tradition of the xUnit family. Specifically, it draws its influence from JUnit and PyUnit (unittest).

Agile-Trac adds the concept of Iterations to Trac which allows a more useful Roadmap view with predicted completion date ranges and relatively sized progress indicators. User stories (and tickets in general) can have one or more completion stages defined for them. These are relatively sized using a sizing scale that you define.

UX strategy is a growing field that promises clearer guidance for UX design projects. Agile UX and lean UX are topics that have caught fire in the world of UX professionals, promising faster delivery and less waste. Do the tenets of rapid iteration and minimal documentation that characterize the lean and agile approaches preclude the research and analysis activities that we typically conduct when formulating UX strategy?

In this article, I introduce the acronym PURIFF as a concept containing all test categories to be conducted during the sprint. The Scrum team can use the PURIFF acronym as a checklist to determine which categories of tests are relevant in the given context.

Sometimes, when testing user stories in Scrum, there's a final Waterfall interaction to deal with. The scenario I present here is based on this situation: a Scrum process with an interaction of sequential phases at the end of the process to (re)test the whole developed functionality. These sequential phases are mandatory for our organization, which follows a Waterfall process for the releases of the product. So, for the moment at least, we have to deal with this and my experience is that we aren't alone.