InfoQ Homepage Software Testing Content on InfoQ
-
Google App Engine Load Test Result
The result of the Google Web Toolkit on Google App Engine load test: The load was 10 reqs/sec for an hour, and 35 reqs/sec at peak. The result? No sweat.
-
Google App Engine public load test today
Today, at 4PM GMT+2 (in about an hour), there is a public load test on the Google App Toolkit. Can Google Web Toolkit and Google App Engine handle the InfoQ effect?
-
Why Traditional Test-Automation Tools Stifle Agility
In recent times, much excitement has circulated about the direction of "next generation functional testing" tools. Alas, many agile organizations still struggle to make their traditional record-and-playback automated testing tools work for them. Elisabeth Hendrickson, aka "test Obsessed", tells them why to stop.
-
Presentation: David Hussman on Automating Business Value with FIT and Fitnesse
In this presentation, David Hussman, founder of DevJam, discusses about user stories, the origin and authoring of story tests, focusing on how FIT and Fitnesse (FIT living within a Wiki) can be used to automate acceptance tests.
-
Interview: Cédric Beust Discusses Designing for Testability
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.
-
Hands-off Load Testing with JMeter and Ant
Automation expert Paul Duvall highlights in a recent post the value of earlier and continuous integration of load tests throughout the development cycle and presents simple step-by-step techniques to create a scheduled integration build that runs JMeter tests.
-
Fixture Gallery, a New Quick Reference For FitNesse How-To
Fixture Gallery is a new open doc cookbook by Gojko Adzic for FIT/FitNesse tests. It provides developers with a quick overview of the most important fixture types and concepts for agile acceptance testing using the FIT framework.
-
Presentation: Designing for Testability
In this presentation from QCon San Francisco 2007, Cedric Beust and Alexandru Popescu discuss interesting features of TestNG such as grouping of tests, data providers for tests and dependency handling in tests, tips for designing easily testable code such as eliminating statics, extreme encapsulation and TDD, the importance of functional versus unit testing, and migrating from JUnit to TestNG.
-
Interview and Book Excerpt: Model Based Software Testing and Analysis with C#
Recently published, Model Based Software Testing and Analyis with C#, by Cambridge University Press. Infoq was able to speak with all four authors about their personal views on model based testing and analysis: Jonathan Jacky, Margus Veanes, Colin Campbell and Wolfram Schulte.
-
Interview and Book Excerpt: Hani Suleiman & Cedric Beust on TestNG
InfoQ.com recently sat down with Hani Suleiman and Cédric Beust the authors of Next Generation Java Testing: TestNG and Advanced Concepts to discuss the book and their thoughts about testing in general. InfoQ is also pleased to offer an excerpt from chapter 2 of the book, "Mocks and Stubs".
-
The Grinder 3.0: "The Programmer's Load Tester" Adds Scripting Support
The Grinder is an open source Java load testing framework that makes it easy to run a distributed test using many load injector machines. Its new release brings significant enhancements including integration with a scripting engine (Jython) that allows flexible test recording, script customization and replay.
-
Test Driven Development or Test Driven Requirements?
Where does one start when practicing test driven development? With the requirements or with the design? Or, put another way, top-down or bottom-up? When one starts to write a test first, without any code, what does that test represent? Both approaches are practiced in the Agile community, but there is little consensus on which provides more value.
-
Debuggers considered Harmful?
A blog post titled "Debugger Support Considered Harmful" claims that Ruby debugging support is lacking - and that that's a good thing. We look at the various rebuttals and the state of Ruby debuggers.
-
What Makes a Tool Agile?
Individuals and interactions over processes and tools is the very first of the values of the Agile Manifesto. Tools, however, seem to be a big part of development on most Agile teams. When does a tool help and when does it hinder (Agile) software development?
-
Review: Continous Performance Management
Steven Haines from Quest has published an article demonstrating the use of performance analysis tools in the continuous build cycle as best practice and makes some thought provoking points about the cost of not doing so.