Index of /archives/NetBSD/NetBSD-release-9/src/external/bsd/openldap/dist/tests/data/regressions
Name Last modified Size Description
![[PARENTDIR]](/icons/back.gif)
Parent Directory -
![[DIR]](/icons/folder.gif)
CVS/ 2025-01-15 12:04 -
![[TXT]](/icons/text.gif)
README 2008-05-22 23:20 1.2K
its4184/ 2024-02-15 03:46 -
its4326/ 2024-02-15 03:46 -
its4336/ 2024-02-15 03:46 -
its4337/ 2024-02-15 03:46 -
its4448/ 2024-02-15 03:46 -
its6794/ 2024-02-15 03:46 -
its8444/ 2024-02-15 03:46 -
its8521/ 2024-02-15 03:46 -
its8616/ 2024-02-15 03:46 -
its8663/ 2024-02-15 03:46 -
its8667/ 2024-02-15 03:46 -
its8752/ 2024-02-15 03:46 -
its8800/ 2024-02-15 03:46 -
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.