Stuart Halloway discusses example-based testing using Simulant, a testing library based on statistical modeling, activity streams, distributed execution, validation, separation of concerns.
Ken Kousen introduces Spock, a logical testing framework written in Groovy, providing code samples for developers.
Les Hatton theorizes the possibility to predict the number of defects in software systems based on the observation that such systems have properties independent of why, how or who implemented them.
Ahmed Syed explains how to use testing and defect management in an Agile project to ensure product quality, addressing design quality, legacy systems, and how build management affects quality.
Ulf Wiger discusses the importance of automated testing along with some lessons learned at Ericsson, including using randomized and extensive testing, aiming to achieve system robustness.
Ben Hall shows how Ruby testing tools can help with .NET and ASP.NET development and takes a look at RSpec, Webrat, Cucumber, Selenium and others. Also: a peek at using IronRuby for testing .NET apps.
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.
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.
Ulf Wiger shows typical Erlang programs, patterns that scale well on multicore and patterns that don't, profiling and debugging parallel applications and ensuring correct behaviour with QuickCheck.
In this talk from RubyFringe, GitHub's Tom Preston-Werner talks about a methodical approach to solving problems and debugging. Also: he explains how to use the "Deathbed Filter" for choosing projects.