openldap/tests/data/regressions
2017-10-05 09:23:02 -07:00
..
its4184 Happy New Year! 2017-01-03 12:36:47 -08:00
its4326 Correctly exit if the backend is back-ldap 2017-02-03 14:30:30 -08:00
its4336 Correctly exit if the backend is back-ldap 2017-02-03 14:30:30 -08:00
its4337 Happy New Year! 2017-01-03 12:36:47 -08:00
its4448 Happy New Year! 2017-01-03 12:36:47 -08:00
its6794 Happy New Year! 2017-01-03 12:36:47 -08:00
its8444 ITS#8444 - Fix description to match the actual issue that was fixed 2017-10-04 20:42:54 -07:00
its8521 Fix comparison error 2017-01-31 16:17:02 -08:00
its8667 ITS#8667 - Add regression test 2017-06-07 11:11:43 -07:00
its8752 Fix script so it exits 2017-10-05 09:23:02 -07:00
README further rewording and clarifications 2006-01-13 11:25:56 +00:00

This directory contains test related to regression tracking that require
a specific setup and a complete test.  Each regression test must be 
contained in a test directory whose name is "its<number>", where <number>
is the ITS number, and it must be entirely executed by a script, contained
in that directory and with the same name of the directory.  It can exploit
all the helpers provided for common tests (variables in scripts/defines.sh,
data files in data/, ...), but it should simultaneously be as self contained
and as general as possible.  Warning: occasionally, data files and
shell variables may change, so limit their use to real needs.

For example, if an issue only appears with a certain database type, the
test itself should only run when invoked for that database type; 
otherwise, if the issue appears whatever backend is used, the test should
be parametric, so that it is run with the backend selected at run-time
via the "-b" switch of the "run" script.

Regression tests are prepared on a voluntary basis, so don't expect all 
bugs to have a test any soon.  When the issue reporter provides a simple,
yet complete means to reproduce the bug she's reporting, this may speed up 
the process.  In case, only put neutral data in bug exploitation reports.