openldap/tests/data/regressions
Quanah Gibson-Mount a3bee86700 Minor wording fix
2020-07-03 15:15:34 +00:00
..
its4184 Happy New Year! 2020-01-09 16:50:21 +00:00
its4326 Happy New Year! 2020-01-09 16:50:21 +00:00
its4336 Happy New Year! 2020-01-09 16:50:21 +00:00
its4448 ITS#9156 Move ppolicy schema into the module 2020-01-23 23:45:41 +00:00
its6794 Happy New Year! 2020-01-09 16:50:21 +00:00
its7573 ITS#7573 Create regression test 2020-04-27 16:21:12 +00:00
its8427 Happy New Year! 2020-01-09 16:50:21 +00:00
its8444 Issue#9020 - Use consistent namespaces for overlays 2020-06-22 20:44:12 +00:00
its8521 Cleanup links to old ITS system 2020-06-21 16:37:48 +00:00
its8616 Cleanup links to old ITS system 2020-06-21 16:37:48 +00:00
its8663 Issue#9020 - Use consistent namespaces for overlays 2020-06-22 20:44:12 +00:00
its8667 Cleanup links to old ITS system 2020-06-21 16:37:48 +00:00
its8752 Cleanup links to old ITS system 2020-06-21 16:37:48 +00:00
its8800 Minor wording fix 2020-07-03 15:15:34 +00:00
README ITS#8605 - spelling fixes 2017-10-11 14:39:38 -07: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 parameteric, 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.