There are several components in an ASP.NET MVC 3 web app – models, controllers, route-handlers, views, html-helpers, client-side code etc. Most of these can be unit-tested, others need integration tests, and several good practices can help you keep your tests more maintainable and avoid making them brittle.
Much of the generally accepted agile literature will advise you that the best way to capture your user's needs is through examples encoded into automated tests - "automated acceptance tests". Thought-leader Jim Shore says maybe not, while others still challenge him.
Is slicing stories in horizontal tasks an Agile Smell? Is this common habit used in Scrum/Agile Planning meetings - hurting a team's focus on customer value? What is being suggested instead?
Stabilization sprints are an additional number of sprints added to the end of the normal development cycle before shipping the product. As the name suggests, they’re usually added to shake down the product one last time and drive the last of the bugs. Do they belong in Agile environment or should "Done" be enough.
Automated tests that are brittle and expensive to maintain have led to companies abandoning test automation initiatives, according to Dale Emery. In a newly published paper, Dale shares some practical ways to avoid common problems with test automation. He starts with some typical automation code and evolves in ways that make it more robust, and less expensive to maintain.
Unit Testing Time and Dates is an often talked about problem with relatively simple solutions. More difficult is the acceptance/system testing with Time. What strategies are used?
InfoQ has interviewed Aslak Hellesøy, the creator of Cucumber on its recent support for .NET. Cucumber is an acceptance testing tool for Behaviour Driven Development (BDD). At Agile2009, InfoQ’s Mark Levison reported from the Functional Test Tools Workshop that Matt Wynne and Richard Lawrence started to work on a .NET solution for Cucumber, later to be named Cuke4Nuke.
A group of people interested in improving the state of the art in Automated Functional Test Tools gathered for an annual workshop the Sunday before Agile 2009. Among the topics covered: Lightening Talk demos of various tools, Porting Cucumber to .NET, Documenting existing functional test tool capabilities in a spreadsheet and the limits of Capture/Playback tools.
There have been sporadic reports of successes in writing requirements as acceptance tests and automating them. This practice is only used by a small minority of the community. Are automated acceptance tests written at the beginning of each iteration just a theoretical assertion that have been proven ineffective by the lack of adoption?
What are the top ten reasons that Tester's love Agile Testing? Kay Johansen recently asked this question and got responses from many of the leading testers.
WatiN is an open-source library for automating web browsers using .NET. WatiN facilitates automated testing of web applications through browser interaction. The recently released WatiN 2.0 CTP3 allows testing through Internet Explorer and FireFox.
Unit and Integration testing often get more importance in Agile teams as compared to acceptance testing. Gojko Adzic and Lisa Crispin suggest approaches to efficiently include acceptance tests as a part of development.
Corey Haines has embarked on a unique personal "Pair Programming Tour". Now three weeks into this innovative journey, Haines has posted video interviews revealing many of the unique insights he's gained about pairing, automated testing, and the evolution of a software craftsman while sharing the keyboard at the home-bases of Dave Chelimsky, Brian Marick, Uncle Bob Martin, and others.
The second Agile Alliance Functional Test Workshop was held as a pre-conference session before Agile 2008. It was run as a series of open space sessions facilitated by Jeff Paton. The primary purpose of this workshop was to discuss cutting-edge advancements in and envision possibilities for the future of automated functional testing tools.
The second Agile Alliance Functional Testing Tools Workshop is being held the day before Agile 2008 (Monday August 4). This is the second workshop being held this year and its goal is “advance the state of the art of automated functional testing tools used by Agile teams to automate customer-facing tests”.