mirror of
https://git.openldap.org/openldap/openldap.git
synced 2026-02-17 01:28:35 -05:00
10566c8be3
* javascript * kernel * ldap * length * macros * maintained * manager * matching * maximum * mechanism * memory * method * mimic * minimum * modifiable * modifiers * modifying * multiple * necessary * normalized * objectclass * occurrence * occurring * offered * operation * original * overridden * parameter * permanent * preemptively * printable * protocol * provider * really * redistribution * referenced * refresh * regardless * registered * request * reserved * resource * response * sanity * separated * setconcurrency * should * specially * specifies * structure * structures * subordinates * substitution * succeed * successful * successfully * sudoers * sufficient * superiors * supported * synchronization * terminated * they're * through * traffic * transparent * unsigned * unsupported * version * absence * achieves * adamson * additional * address * against * appropriate * architecture * associated * async * attribute * authentication * authorized * auxiliary * available * begin * beginning * buffered * canonical * certificate * charray * check * class * compatibility * compilation * component * configurable * configuration * configure * conjunction * constraints * constructor * contained * containing * continued * control * convenience * correspond * credentials * cyrillic * database * definitions * deloldrdn * dereferencing * destroy * distinguish * documentation * emmanuel * enabled * entry * enumerated * everything * exhaustive * existence * existing * explicitly * extract * fallthru * fashion * february * finally * function * generically * groupname * happened * implementation * including * initialization * initializes * insensitive * instantiated * instantiation * integral * internal * iterate |
||
|---|---|---|
| .. | ||
| its4184 | ||
| its4326 | ||
| its4336 | ||
| its4337 | ||
| its4448 | ||
| its6794 | ||
| its8444 | ||
| its8521 | ||
| its8667 | ||
| its8752 | ||
| README | ||
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.