head     1.1;
branch   1.1.1;
access   ;
symbols  OPT_20031204:1.1.1.1 OPEN_POSIX_TESTSUITE:1.1.1;
locks    ; strict;
comment  @# @;


1.1
date     2003.12.31.09.14.35;  author mtm;  state Exp;
branches 1.1.1.1;
next     ;

1.1.1.1
date     2003.12.31.09.14.35;  author mtm;  state Exp;
branches ;
next     ;


desc
@@



1.1
log
@Initial revision
@
text
@BOUNDARY TESTS
==============
It is sometimes useful to test parameter boundaries as part of API testing.
In the POSIX Test Suite Framework, variables cannot be assigned to values that
would cause warnings (because warnings are treated as errors), so the following
list of boundary values has been created for boundary testing.

These boundary values are those values that the gcc compiler would set an 
invalid parameter to during compile time:

INT32_MAX+1       -2147483647 (gcc compiler gave -2147483648)
INT32_MIN-1        2147483647
unassigned val    -1073743192
unassigned val     1075002478

Potentially the MAX+1/MIN-1 values are deterministic.  The others are just
empirical examples.

Contributors:	julie.n.fleischer REMOVE-THIS AT intel DOT com
		geoffrey.r.gustafson REMOVE-THIS AT intel DOT com
@


1.1.1.1
log
@Initial import of the Open Posix Test Suite (http://posixtest.sourceforge.net).
@
text
@@
