Visual Test

From Wikipedia, the free encyclopedia

There are very few or no other articles that link to this one.
Please help introduce links in articles on related topics. After links have been created, remove this message.
This article has been tagged since June 2006.

Visual Test started as MS-Test from Microsoft. It was a method for Microsoft to automate some of the testing of its applications. At the time Microsoft was looking to start another revolution in the personal computer world with the release of Windows.

1 Overview
2 Capabilities
- 2.1 32 bit enhancements
3 References

[edit] Overview

This tool was to advance the process of testing window applications beyond the point and click of objects on windows. This was initially done with the Windows tool: Recorder. It achieved this by combining a Windows development language Basic with a testing oriented API. MS-Test had its initial release at the beginning of 1992.

As a Microsoft language, tests known as scripts were written in Test Basic, a form of the BASIC programming language. The API was predominantly wrapped around Windows API functions. While test scripts could be created with capture/replay, its dominant strength was that scripts could be coded and compiled. Either an individual script could be run, or a group of them run in sequence by a test driver. Among the innovations for the test driver was the ability to customize the batch execution with the inclusion of custom designed dialog boxes and menus. These were built with the User Interface Editor.

While Visual Test always retained the $795 price for the ability to develop scripts, it offered the free and unlimited redistribution of compiled scripts. The ability to use OLE Automation allowed enterprising individuals to expand beyond the basic functional testing into load testing. A script could create 10's of browsers, drive them, feed them with data, collect statistics and monitor the state of the test.

[edit] Capabilities

As with any tool new capabilities were added over time. In 1992 new DLLs were added to provide support for testing

DOS VM
DDE (Dynamic Data Exchange)
The ability to run scripts remotely on other PCs of a local LAN.
An enhanced test driver

Included with Visual Test were a great suite samples that demonstrated the range of capabilities of the product.

Play the minesweeper game on its own.
Play solitaire
Sample screensaver and others.

[edit] 32 bit enhancements

In 1994 MS-Test as Version 3.0 advanced from the 16-bit world to the 32-bit. Version 2.0 in 1993 had provided support for Windows 3.1. With Version 4.0 in 1995 it was hosted within an encompassing environment, Visual Studio and became known as Visual Test. It was able to support the testing of the new application control that arrived with Windows '95 and NT. Interestingly the other development language, Visual Basic remained hosted within it own separate development environment. With its inclusion in Visual Studio, versioning of scripts could be maintained with the other Studio tool, Visual Source Safe. In an update, 4.0, the ability to access its capabilities from Visual Basic and C++, lost with 4.0, was regained.

As 4.0r was being released the Rational negotiated its purchase from Microsoft. Version 6 (5 was skipped) from Rational incorporated support for a Microsoft technology, MSAA (Microsoft Active Accessibility). A more visual enhancement for this version was support for HTML and Web pages. At Rational, Visual Test became exposed to the other tools offered: Purify, Quantify and ClearCase. A version was ported to support Unix for the Sparc.

In 1998, version 6.0 provided support for Windows 98 and NT 5.0. It was now hosted in the Microsoft Developer Studio and gained the ability to read and change the Registry. Rational remained committed to fully support Visual Test through 2002. The 103 Tech Notes that were provided as part of the support from Rational, remain available in 2006 from IBM, which previously acquired Rational ([[1]]).