During a panel discussion about Behaviour-Driven Development (BDD) at this year’s CukeUp 2015 conference Dan North came up with an idea of a community-curated resource for everyone interested in BDD with examples, adaptions, scenarios as well as experience reports and common practises and links to other external resources.
Fran O'Hara's lessons learned integrating testing in agile teams, in particular ensuring required test competencies are in place. Full test integration in an agile team is not as simple as mixing a couple of testers in the team, instead multiple working practices and skills are needed for delivering quality applications in an agile world.
Cucumber was created as a way to overcome ambiguous requirements and misunderstandings, targeting both non-technical and technical members of a project team, but if you think Cucumber is a testing tool you are wrong, Aslak Hellesøy, who created Cucumber in 2008, recently stated. Julien Biezemans and Liz Keogh recently expressed similar opinions.
Testdroid's maker Bitbar has recently announced the integration of Testdroid mobile app testing products with Atlassian JIRA defect tracking system. InfoQ has interviewed Testdroid technical product manager Ville-Veikko Helppi to better understand how developers and organizations could benefit from it.
Apple confirmed that it acquired Burstly, the owner TestFlight. TestFlight is a beta-testing platform for mobile applications which offers easy-to-use services to help in the process of distributing and testing apps for iOS and Android. Whereas TestFlight will continue to support iOS applications, testing of Android apps will be discontinued by March 21st.
Cucumber Pro, an online collaboration and reporting platform on top of the popular BDD tool Cucumber, has been unveiled by the core maintainers of Cucumber. The new tool will target enterprises that require official tool support.
The Agile Alliance Functional Testing Tools (AA-FTT) workshop was held on the day before the Agile 2012 conference in Dallas, Texas. Run as an open space, the session was open to anyone interested in talking about the future of functional testing tools and beyond.
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?