Visual Test

Last updated
Visual Test
Developer(s) Microsoft, Rational Software
Initial release1992;30 years ago (1992)
Operating system Windows
Available inEnglish
License Proprietary

Visual Test, originally known as MS-Test, was an automated testing tool for Windows applications developed by Microsoft and later sold to Rational Software.

Contents

Overview

MS-Test was developed for internal use in Microsoft but became a commercial product at the beginning of 1992. MS-Test automated the process of testing Windows applications. It combined a Windows development language, Basic, with a testing-oriented API.

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. Test scripts could be created with capture/replay, in particular by the Windows Recorder tool. However 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, which were built with the User Interface Editor.

Customers had to purchase Visual Test to develop scripts, but it offered free and unlimited redistribution of compiled scripts. The ability to use OLE Automation allowed enterprising individuals to expand beyond basic functional testing into load testing. A script could create tens of browsers, drive them, feed them with data, collect statistics and monitor the state of the test.

Capabilities

New capabilities were added over time. In 1992, new DLLs were added to provide support for testing:

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

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

  1. Play the minesweeper game on its own.
  2. Play solitaire
  3. Sample screen saver and others

32-bit enhancements

Version 2.0 in 1993 had provided support for Windows 3.1. In 1994 MS-Test version 3.0 advanced from 16-bit systems to 32-bit. With Version 4.0 in 1995, it was hosted within Visual Studio and renamed to Visual Test. It was able to support the testing of the new application control that arrived with Windows 95 and NT. The other development language, Visual Basic, remained hosted within its own separate development environment. With its inclusion in Visual Studio, versioning of scripts could be maintained with Microsoft Visual SourceSafe, also part of Studio. In version 4.0, the ability to access its capabilities from Visual Basic and C++, lost with 3.0, was regained.

As 4.0r was being released, Rational Software Corporation negotiated its purchase from Microsoft in 1996. [1] Version 6 (5 was skipped) from Rational incorporated support Microsoft Active Accessibility (MSAA), support for HTML and Web pages and ability to read and change the Windows Registry. Version 6 provided support for Windows 98 and NT 5.0, which eventually became Windows 2000.

Mainsoft Corporation created a ported version called MainWin Visual Test 4.0r for Unix. This version is for testing Unix applications created from Windows applications using Mainsoft MainWin platform.

Rational Visual Test 6 was also sold as part of Rational DevelopmentStudio bundle. Visual Test was integrated with other Rational products: Purify, and Quantify, PureCoverage and ClearCase. Rational remained committed to fully support Visual Test through 2002. The last version shipped was 6.5.

As of 2006, 103 tech notes that were provided as part of the support from Rational remained available from IBM, which previously acquired Rational (Search results).

Notes

  1. www.microsoft.com https://web.archive.org/web/20080406121859/http://www.microsoft.com/presspass/press/1996/oct96/ratvtstpr.mspx. Archived from the original on April 6, 2008.{{cite web}}: Missing or empty |title= (help)

Related Research Articles

DirectX Collection of multimedia related APIs on Microsoft platforms

Microsoft DirectX is a collection of application programming interfaces (APIs) for handling tasks related to multimedia, especially game programming and video, on Microsoft platforms. Originally, the names of these APIs all began with "Direct", such as Direct3D, DirectDraw, DirectMusic, DirectPlay, DirectSound, and so forth. The name DirectX was coined as a shorthand term for all of these APIs and soon became the name of the collection. When Microsoft later set out to develop a gaming console, the X was used as the basis of the name Xbox to indicate that the console was based on DirectX technology. The X initial has been carried forward in the naming of APIs designed for the Xbox such as XInput and the Cross-platform Audio Creation Tool (XACT), while the DirectX pattern has been continued for Windows APIs such as Direct2D and DirectWrite.

The Portable Operating System Interface (POSIX) is a family of standards specified by the IEEE Computer Society for maintaining compatibility between operating systems. POSIX defines both the system- and user-level application programming interfaces (API), along with command line shells and utility interfaces, for software compatibility (portability) with variants of Unix and other operating systems. POSIX is also a trademark of the IEEE. POSIX is intended to be used by both application and system developers.

Visual Basic for Applications (VBA) is an implementation of Microsoft's Event-Driven Programming language Visual Basic 6.0 built into most desktop Microsoft Office applications. Although based on pre-.NET Visual Basic, which is no longer supported or updated by Microsoft, the VBA implementation in Office continues to be updated to support new Office features. VBA is used for professional and end-user development due to its perceived ease-of-use, Office's vast installed userbase, and extensive legacy in business.

Microsoft Developer Network (MSDN) was the division of Microsoft responsible for managing the firm's relationship with developers and testers, such as hardware developers interested in the operating system (OS), and software developers developing on the various OS platforms or using the API or scripting languages of Microsoft's applications. The relationship management is situated in assorted media: web sites, newsletters, developer conferences, trade media, blogs and DVD distribution.

Graphics Device Interface Microsoft Windows API

The Graphics Device Interface (GDI) is a legacy component of Microsoft Windows responsible for representing graphical objects and transmitting them to output devices such as monitors and printers. Windows apps use Windows API to interact with GDI, for such tasks as drawing lines and curves, rendering fonts, and handling palettes. The Windows USER subsystem uses GDI to render such UI elements as window frames and menus. Other systems have components that are similar to GDI; for example: macOS has Quartz, and Linux has X Window System and Wayland.

In computing, the Windows Sockets API (WSA), later shortened to Winsock, is an application programming interface (API) that defines how Windows network application software should access network services, especially TCP/IP. It defines a standard interface between a Windows TCP/IP client application and the underlying TCP/IP protocol stack. The nomenclature is based on the Berkeley sockets API used in BSD for communications between programs.

JScript is Microsoft's legacy dialect of the ECMAScript standard that is used in Microsoft's Internet Explorer 11 and older, that has multiple security bugs "exploited by nation-state actors", leading Microsoft to add an option to disable it.

Windows Script Host Automation Technology for Windows

The Microsoft Windows Script Host (WSH) is an automation technology for Microsoft Windows operating systems that provides scripting abilities comparable to batch files, but with a wider range of supported features. This tool was first provided on Windows 95 after Build 950a on the installation discs as an optional installation configurable and installable by means of the Control Panel, and then a standard component of Windows 98 and subsequent and Windows NT 4.0 Build 1381 and by means of Service Pack 4. The WSH is also a means of automation for Internet Explorer via the installed WSH engines from IE Version 3.0 onwards; at this time VBScript became means of automation for Microsoft Outlook 97. The WSH is also an optional install provided with a VBScript and JScript engine for Windows CE 3.0 and following and some third-party engines including Rexx and other forms of Basic are also available.

Windows Management Instrumentation (WMI) consists of a set of extensions to the Windows Driver Model that provides an operating system interface through which instrumented components provide information and notification. WMI is Microsoft's implementation of the Web-Based Enterprise Management (WBEM) and Common Information Model (CIM) standards from the Distributed Management Task Force (DMTF).

Microsoft Visual Studio Express Integrated development environment

Microsoft Visual Studio Express is a set of integrated development environments (IDEs) that Microsoft developed and released free of charge. They are function-limited version of the non-free Visual Studio and require mandatory registration. Express editions started with Visual Studio 2005.

Windows NT 3.1 Major release of Windows NT

Windows NT 3.1 is the first major release of the Windows NT operating system developed by Microsoft, released on July 27, 1993.

Interix was an optional, POSIX-conformant Unix subsystem for Windows NT operating systems. Interix was a component of Windows Services for UNIX, and a superset of the Microsoft POSIX subsystem. Like the POSIX subsystem, Interix was an environment subsystem for the NT kernel. It included numerous open source utility software programs and libraries. Interix was originally developed and sold as OpenNT until purchased by Microsoft in 1999.

Microsoft Data Access Components Framework

Microsoft Data Access Components is a framework of interrelated Microsoft technologies that allows programmers a uniform and comprehensive way of developing applications that can access almost any data store. Its components include: ActiveX Data Objects (ADO), OLE DB, and Open Database Connectivity (ODBC). There have been several deprecated components as well, such as the Jet Database Engine, MSDASQL, and Remote Data Services (RDS). Some components have also become obsolete, such as the former Data Access Objects API and Remote Data Objects.

Dependency Walker or depends.exe is a free program for Microsoft Windows used to list the imported and exported functions of a portable executable file. It also displays a recursive tree of all the dependencies of the executable file. Dependency Walker was included in Microsoft Visual Studio until Visual Studio 2005 and Windows XP SP2 support tools. The latest version v2.2.10011 is not available on dependencywalker.com website but is included in the Windows Driver Kit v10.

Active Scripting is the technology used in Windows to implement component-based scripting support. It is based on OLE Automation and allows installation of additional scripting engines in the form of COM modules.

In Microsoft Windows applications programming, OLE Automation is an inter-process communication mechanism created by Microsoft. It is based on a subset of Component Object Model (COM) that was intended for use by scripting languages – originally Visual Basic – but now is used by several languages on Windows. All automation objects are required to implement the IDispatch interface. It provides an infrastructure whereby applications called automation controllers can access and manipulate shared automation objects that are exported by other applications. It supersedes Dynamic Data Exchange (DDE), an older mechanism for applications to control one another. As with DDE, in OLE Automation the automation controller is the "client" and the application exporting the automation objects is the "server".

Visual Basic (classic) Event-driven programming language

The original Visual Basic is a third-generation event-driven programming language from Microsoft known for its Component Object Model (COM) programming model first released in 1991 and declared legacy during 2008. Microsoft intended Visual Basic to be relatively easy to learn and use. Visual Basic was derived from BASIC and enables the rapid application development (RAD) of graphical user interface (GUI) applications, access to databases using Data Access Objects, Remote Data Objects, or ActiveX Data Objects, and creation of ActiveX controls and objects.

Azure DevOps Server is a Microsoft product that provides version control, reporting, requirements management, project management, automated builds, testing and release management capabilities. It covers the entire application lifecycle, and enables DevOps capabilities. Azure DevOps can be used as a back-end to numerous integrated development environments (IDEs) but is tailored for Microsoft Visual Studio and Eclipse on all platforms.

Microsoft Visual Studio Code editor and IDE

Microsoft Visual Studio is an integrated development environment (IDE) from Microsoft. It is used to develop computer programs, as well as websites, web apps, web services and mobile apps. Visual Studio uses Microsoft software development platforms such as Windows API, Windows Forms, Windows Presentation Foundation, Windows Store and Microsoft Silverlight. It can produce both native code and managed code.

.NET Framework version history

Microsoft started development on the .NET Framework in the late 1990s originally under the name of Next Generation Windows Services (NGWS). By late 2001 the first beta versions of .NET 1.0 were released. The first version of .NET Framework was released on 13 February 2002, bringing managed code to Windows NT 4.0, 98, 2000, ME and XP.

References