Tracking change and innovation in the enterprise software development community
Scaling Scrum
in the enterprise?
ScrumWorks Pro
can help.
Start a trial today
Free Book Offer
SOA Demystified
$40 Value
QCon London 2010!
March 10-12, 100
Speakers, 80 sessions,
"THE" team leads and,
architects conference.
In this presentation, Jason Huggins discusses why Selenium exists, Selenium as a functional testing tool, problems with using Selenium, the history of Selenium, JWebUnit, DriftWood, JsUnit, Fit, Selenium core, Selenium IDE, Selenium Remote Control, Selenium Grid, issues encountered doing functional testing in the browser, and Selenium hacks to work around these issues.
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.
James Bach and Elisabeth Hendrickson are two of the context driven testing community. James recently spoke at the STANZ conference and provided a guideline for approaching testing, and Elisabeth provides a heuristic checklist to help identify valuable testing activities.
Following are the most relevant excerpts from the interview with James Bach at Oredev 2008. He covers topics like: engineering, why we should be telling success stories, opening our minds to other scientific domains, automated testing and exploratory testing.
Dependency Injection by Dhanji R. Prasanna is a book that tries to explore the DI idiom in detail, and present techniques in Spring and Guice. Dhanji is a Google software engineer who works on Google Wave and also contributes to Guice, MVEL, and other open source projects.
In this talk from FutureRuby, Joseph Wilk gives an introduction to the BDD framework Cucumber and gives valuable tips for getting it adopted and used by customers and developers.
Integration tests are a scam. You’re probably writing 2-5% of the integration tests you need to test thoroughly. You’re probably duplicating unit tests all over the place. Your integration tests probably duplicate each other all over the place. When an integration test fails, who knows what’s broken? Learn the two-pronged attack that solves the problem: collaboration tests and contract tests.
In this interview filmed during RubyFringe 2008, Luke Francl explains his position towards testing. While supporting unit testing, he thinks testing is not going to reveal all application defects. Development teams should also practice code reviews and usability tests which are likely to discover bugs not visible though other methods.
In this interview from QCon San Francisco 2007, Cédric Beust discusses designing and architecting for testability, problems that hinder testability, test-driven development, the "Next Generation Testing" book, performance testing recipes, and testing small, medium and large codebases.
This book guides the reader on crafting their own agile adoption strategy focused on their business values and environment. This strategy is then directly tied to patterns of agile practice adoption that describe how many teams have successfully (and unsuccessfully) adopted them. Business values are also a component of these patterns so your adoption is always focused on addressing your particular environment.
