InfoQ Homepage Testing Content on InfoQ
-
What do you do, Testing or Checking?
Software testing is an empirical investigation conducted to provide stakeholders with information about the quality of the product or service under test. However, this definition does not talk about sapience which brings about a subtle difference between testing and checking. Michael Bolton talked about this difference and the reason why there should be a difference between the two.
-
System/Acceptance Testing with Time and Dates
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?
-
Test Driven Development and the Trouble with Legacy Code
Alan Baljeu was trying to use TDD with his large, legacy C++ code base. He found that the principle of the simplest thing that could possibly work was causing him trouble with the amount of rework.
-
Metrics for Ruby With Caliper
Caliper calculates various metrics – for example code duplication and complexity – for your Ruby code; all you need is a public Git repository.
-
Uncle Bob On The Applicability Of TDD
Following up a pot-stirring blog where he asserted that "anyone who continues to think that TDD slows you down is living in the stone age", Bob Martin takes a stab at providing some deeper insight into the real applicability, role, and benefit of TDD.
-
Agile Testing Requires Cross-Functional Teams and More
The first things many think about when considering Agile Testing are tools, automation, when and how to test, and the role of testers on a team. These are all very worthy topics. But which of these things are needed for success and which are nice-to-have?
-
Testing Heuristics - Thinking like a tester
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.
-
Introducing Coulda - Evolutionary Behavior Driven Development with Ruby
It is often the case, a new piece of software is developed by someone who needed to fill a void left by an existing product. Software evolves from tools we use which don't exactly meet our needs, this is the case with a new Behavior Driven Development (BDD) tool called Coulda, developed by Evan Light.
-
Functional Test Tools Workshop
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.
-
Faster Ruby Test Execution With Devver
Devver is a new service that runs your Ruby tests in parallel on their cloud infrastructure. InfoQ talked to Ben Brinckerhoff from Devver to understand how they can speed up your tests.
-
Categorizing Tests
What's the difference between unit tests, functional tests, system tests and integration tests? What about developer tests, story tests, and acceptance tests? There seems to be no consensus on naming and categorization of tests although they are central to many Agile development processes. A discussion on the TDD discussion group examines these categorizations and attempts to clear the waters.
-
Guidelines for Better Unit Tests
Jimmy Bogard, Charlie Poole, Lior Friedman, Charlie Poole and others give their guidelines for more readable and useful unit tests.
-
Kent Beck Suggests Skipping Testing for Very Short Term Projects
Kent Beck suggests that on very short term projects, when you're trying to figure out if there is a viable concept, you might do less (even no) automated testing to help get off the ground quickly. This goes against all of the conventional wisdom surrounding TDD.
-
Automated Acceptance Tests - Theoretical or Practical
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?
-
Top Ten Reasons to Love Agile Testing
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.