/*
                           HISTORY:
                           Author: Detlef Wolf  July 20 1995
                           Updated by Jean Thierry-Mieg, April 1996
			   Maintained by Fred Wobus, June 1999

      Partial Behavioural Specification for the Textual Version
               of the ACEDB Database Management System

contents
0. introduction
1. basic tests (load, dump, simple queries)
2. constructed types
3. attached queries
4. tables
5. misc


initial version: detlef wolf  may 1995  Geyserville
these test were compiled with hints from
Natassa Spiridou, Karen Davis, Richard Durbin and Otto Ritter,
Martin Senger, the LBL bug archive and sure I forgot somebody

-----------------------------------------------------------------------

0. introduction

This is a behavioural specification of some important features of ACEDB.
There are three views on this text: the view of the person documenting
and testing ACEDB -- he edits this script, the view of the person writing
ACEDB -- he gets the bug report, and finally the view of the automatic
tester that determines functional differences between
two ACEDB version -- it reads the script part.
I can imagine a fourth view: It can be read by novice ACEDB programmers
who want to understand ACEDB's features. (It could be structured
into chapters for that purpose)

According to these needs, each behaviour is described by several paragraphs:

:SUMMARY: one line test purpose
:NAME: unique short test id for references, automatically taken
       from the first dbinit command in the script
:PRIORITY: 1=low, 2=middle, 3=high, ...
:STATUS:  fail / ok
:FEATURE: long description (/w input data and model excerpt)
:HISTORY: who created this test, who modified it and why
:DATA:  which data is used
:MODEL: relevant part of the model used
:RESULT: what is done (in plain english) and what is the outcome;
         for failures describe the difference from the correct behaviour
:SCRIPT: that implements the test

Each description block begins with a line beginning with /* :SUMMARY:
and ends with :SCRIPT: */  (the */ must be at the end of the line
to be recognized). The order of the :tags: is not important except
for SUMMARY and SCRIPT.

The description must be human-readable and good enough for the
developer to understand the bugs.
*/

// sample block for test descriptions (remove the - signs, then 
// copy and reuse, please):
/* -:SUMMARY: 
:PRIORITY: 1
:STATUS: ok
:FEATURE: 
:HISTORY: 
:MODEL: 
:DATA: 
:RESULT: 
works in: ace33f, ace950716
fails in: ace33f 
-:SCRIPT: */




// -------------------------- 1. basic tests (load, dump, simple queries)

include tagvqry
include newname
include stacksiz
include escape
include longline
include comments
include quotes
include nnmqry
include abnmqry
include grep
include parsstop
include ppcont
include emptyo
include qcount
include intag
include xrefct
include followct
include ctdel
include nestcoq
include atqry
include aqdump
include cttab
include tables
include tabpre
include alias
include clacse
include parsubq
include anyxref
include crashq
include ocount
include rclass
include cnstrain
include parseat

/*************************** eof ****************************/