Benefits of TAME

Everyone agrees that comprehensive testing is key to delivering reliable software.

But there never seems to be enough time (or money or people) for adequate testing.

Rapid cycle times brought on by the adoption of agile approaches only seem to make things worse.

Even with automated systems for running tests, you're still left with the time-consuming, mundane, and repetitive job of creating many test cases.

Who can use TAME

TAME bridges the gap between analysts and testers by presenting each function in terms of preconditions, inputs, actions, and results—exactly the same way an analyst might write a use case or user story.

TAME helps the analyst to think through what needs to be tested.

TAME gives the tester a platform for creating many test cases quickly.

TAME gives the project manager a means for sizing and scoping the testing effort.

Where to use TAME

TAME throughout the software lifecycle:

Unit testing

specify and generate test cases that can run against software modules (classes, functions).

GUI testing

whether a traditional installed application, a website, or a mobile app, use TAME to specify the contents of UI pages, then generate test cases to validate user-facing behavior.

Regression testing

update the test specification and the test cases whenever new features are deployed or bugs are fixed.

Project planning

create initial test specifications to estimate the number of test cases to be run and project the cost of the test effort.

Retrospectives

use the test specifications to probe features to better understand the root causes of failures.