Acceptance testing specification

Acceptance testing specification


Document formatted by vherva at Fri Apr 24 11:23:17 1998 on the host schemestation. This document is produced by the SchemeStation project during the Tik-76.115 course.

1 Introduction

This document describes the SCHEMESTATION acceptance testing. The purpose of the system testing is to ensure that the SCHEMESTATION simulation implements the fearures requested by the client. Unlike normally the acceptance testing of the product is not performed by the client, but the implementors. This is done by running applications on top of the environment provided by the SCHEMESTATION.

The acceptance testing is gained to represent "visually" the working migration and its benefits. With working migration represtented with these tests and system testing performed, the client can be practically sure about the quality and functionality of the product.

The migration tests are considered to be a part of the acceptance testing.

2 The Travelling Agent

The functionality and performance of the system is tested with the "travelling agent." The agent gathers data from a set of information sources (typically, file servers in object servers).

The test program is implemented with SS Scheme, allowing to take some measure of "ease" of writing such agents to the system.

2.1 Functionality

The agent has two variations: the travelling version and the remote-gather version. The difference between these is that the travelling agent migrates itself to the same domain as the object (and file) server next processed, when remote-gather version doesn't.

The basic functionality is:

  • Connect a file server specified next in the batch list.
  • Gather specified file(s).
  • Count number of rows from the files, and store that information to the result list.
  • Close connections
  • Process next batch list item.

After the batch job is done, results are printed (or written into a file).

2.2 Performance

Benefits of migration are considered by measuring performance of the batch job. This is performed by measuring execution time for variations of the test; the travelling and the remote-gather, and also versions that process files in certain size scales. This way migration costs can be measured, and obviously domains where some of the above techniques is superior to each other.


© SchemeStation project 1997-1998 [Back to the document index]