This post is aimed at a specific group of us that need to show full test to requirements coverage in Mercury Quality Center or Test Director.

I've always been annoyed that Test Director and now Quality Center will not let you designate a requirement that is just a category for holding real requirements as something that did not need to be covered by a test. This always led to questions by management and processs auditors as to why we didn't have 100% coverage when they looked at our coverage graphs, even though we had all the real requirements covered. If you have a complicated tree, those requirement holders can eventually add up to a high percentage showing as "Not Covered", and it can be difficult to prove quickly that all uncovered requirements are just categories.

How would you like it if this happened? Have HTTP::Recorder to create scripts on fly to work with SAMIE module. Personally, i think it would be great to have such recording functionality. But as we know, HTTP::Recorder doesn't support SSL or javascript.... would that effects your tests? really?... Think again...


One way of avoiding/bypassing SSL restriction i could think of is to simply record the scripts with SSL disabled, and then manually just go in and change http to https....

On Tuesday I attended Mercury NYC Local User Group. There were two presentations from Mercury – product update and business process testing. Most people were interested in functional testing.

Some things that were interesting for me:
- Mercury plans integration with the new VisualStudio, no details
- New TestDirector (for Quality Center 8.2) is re-written to J2EE, multiplatform now
- Quality Center 8.2 includes Actuate reports

TextTest is an application-independent tool for text-based functional testing. This means running a batch-mode binary in lots of different ways, and using the text output produced as a means of controlling the behaviour of that application.

FatCow is a set of macros for use with Confluence. FatCow allows the user to simply write web testcases within a Confluence page. Tests are defined in a table and allow the user to perform functions like navigate to a url, assert values on a page, fill-in and submit forms and click links on a page. Once the tests are run FatCow produces an aggregated report of the test results.

Latka is a functional (end-to-end) testing tool. It is implemented in Java, and uses an XML syntax to define a series of HTTP (or HTTPS) requests and a set of validations used to verify that the request was processed correctly.

Pounder is a utility for automating Java GUI tests. It allows developers to dynamically load GUIs, record scripts, and then use those scripts in a test harness.

Pounder differentiates itself from other utilities by allowing you to examine the results of a test run in source, while maintaining a separate GUI script that can be re-recorded if necessary.

From the home page: "Selenium is a testing tool for browser-based testing of web applications. It can be used both for functional and compatability testing. Selenium tests run directly in supported browsers, just as real users do."

Driven by test-definition tables, similarly to FIT/FitNesse, it provides simple keyword driven interactions with the web-application front-end.

Se