I'd like for more of my colleagues to write unit tests. My motives are selfish. Unit tests help me figure out how methods of the unit are supposed to work. Unit tests are documentation too. And if a unit is testable, that makes it pretty good code. I believe one reason that some of my fellows don't write unit tests is because they're not quite sure how the mock object thing fits in. I'll explain.
The Tellurium Automated Testing Framework (Tellurium), formally known as the Abstract Object based Selenium Test framework (AOST), is a test framework built on top of the Selenium test framework and it abstracts UI components to Java objects and does object to locator mapping (OLM) automatically at run time so that you can define UI objects simply by their attributes and write your selenium tests just like writing Java tests.
Gant is a build tool for scripting Ant tasks using Groovy instead of XML to specify the build logic. A Gant build specification is a Groovy script and so can bring all the power of Groovy to bear directly, something not possible with Ant scripts. Whilst it might be seen as a competitor to Ant, Gant uses Ant tasks for many of the actions, so Gant is really an alternative way of doing builds using Ant, but using a programming language rather than XML to specify the build rules.
The Reengineering Forum ("REF") is an industry association to encourage combined industry/research review of the state of the art and the state of the practice in reengineering of software, systems, and business processes. It is a meeting place for key people in the reengineering and reverse engineering fields: developers, researchers, and leading-edge users.
StoryTeller is a new tool for efficient creation and management of automated testing of .Net code with the NFit/FitNesse engine. StoryTeller is specifically created to support an Acceptance Test Driven Development strategy. All existing .Net FitNesse tests will run under StoryTeller. Features will include editing, tagging, and integration with source control, CruiseControl.Net, NAnt and/or MSBuild, and support for application versioning.
Applying Root Cause Analysis (RCA) to software problems is fundamentally different from applying it to other engineering disciplines. Rather than analyzing a single major failure, we are usually analyzing a large number of failures with software. In this week's column, Ed Weller explains how to use RCA to your advantage.
Exploratory testing--questioning and learning about the product as you design and execute tests rather than slavishly following predefined scripts--makes sense for many projects. But does it make sense for agile projects? In this week's column, Johanna Rothman examines how exploratory testing might work on an agile project.
Qualify - SQA Design's Test Case Management solution offers a robust set of features at a price you can afford. SQA design offers solutions for Software Testing Techniques and methods