Home · About · A-Z Index · Search · Contacts · Press · Register · Login

VSU 4 Overview


 

You are here:  Testing > Test suites > VSU4 Overview

Additions for Single UNIX Test Suite

VSU5 is now available and is able to operate in two modes UNIX 95 and UNIX 98


Summary

  • Verifies the UNIX® extensions to the core operating system calls and libraries
  • The industry standard test suite for Sockets, Curses and traditional UNIX system extensions
  • Test Coverage: Sockets, STREAMS, System interface extensions, Curses
  • Over 4000 tests (excluding Curses)
  • Mandatory for testing the Single UNIX® Specification.

Top


Introduction

The X/Open Single UNIX Extensions Test Suite, known as VSU4, tests the Single UNIX Extensions over XPG4 Base, which is tested by VSX4.

VSU4 uses the industry standard Test Environment Toolkit (TET) as its test harness. The TET is described elsewhere.

Top


Disk Space Requirements

Disk space requirements on a typical CISC based system are as follows:

  • Source code - 40 Mbytes
  • Source and tests built - 200 Mbytes (on a CISC system)

Numbers of tests, and time to run

UNIX Test Mode - over 4,000 tests

Note than when the X/Open Curses tests are mandated this will increase the test suite to approximately 8,000 tests.

A typical test run from start to finish takes approximately 10 hours on an Intel Pentium based system.

Top


Test Coverage

The VSU test suite verifies the compliance of systems to the Single UNIX Specification extensions for the core kernel and library interfaces (VSX4 has to be used in addition) . VSU4 verifies over 450 new interfaces added to X/Open's XPG4 specifications for the Single UNIX Specification.

VSU features include:

  • The industry's first tests for the popular sockets and STREAMS networking interfaces. These interfaces are key to the development of portable client server applications
  • Extensive tests for development environments, ensuring a common application can be installed and built across systems bearing the UNIX trademark=
  • Tests for many interfaces originating in common UNIX variants: UNIX System V, BSD UNIX and OSF/1, providing a unified application environment across all these Operating Systems
  • Tests for the widely used CURSES terminal user interface package.

Top

Modular Design

VSU4 is modular, both at the implementation level and at the user level. The testing process is divided into clear stages -

Each stage is clearly documented in the VSU User and Installation Guide, which accompanies the product.

Preparation

This stage includes setting up user-ids and groups for testing, and reading the tape. This stage includes configuring and installing the TET harness, which is used to control building, execution and cleanup of VSU tests.

Configuration and Installation

VSU automatically installs on most common platforms. Where system dependencies may vary, these are isolated into clearly defined user changeable sections of the test suite. During this stage VSU4 builds the test harness and associated libraries.

Test Building

VSU separates the building of the test harness and tools from the testsets themselves. The test suite may be built completely or in sub-sections, which decrease in granularity from test sections and areas down to individual testsets.

Test Execution

Once built, the test suite may be run as a whole in one pass, or in sub-sections which decrease in granularity from test areas down to individual tests within testsets. If you are producing an X/Open branding application the test suite must run in a single uninterrupted pass.

It is possible to combine the building and execution phases into a single pass, and this is the recommended way for a formal X/Open branding application.

Test Reporting

VSU generates an intermediate level journal file in a TET compliant format. This is sufficient for debugging purposes. When a formal report is required, such as for X/Open branding then the formal report writers provided with VSU are used to process the journal file.

Top



Home · Contacts · Legal · Copyright · Members · News
© The Open Group 1995-2012  Updated on Thursday, 11 September 2003