Skip to content
Permalink
Browse files
update description to current
  • Loading branch information
shawnmckinney committed Nov 13, 2021
1 parent 901c22d commit 704fa351395f6b41b63ccb851170a0e125953edf
Showing 1 changed file with 2 additions and 9 deletions.
@@ -30,23 +30,16 @@
/**
* This JUnit test class drives all of the Fortress Administration APIs contained within {@link AdminMgrImplTest},
* {@link DelegatedMgrImplTest}, {@link org.apache.directory.fortress.core.impl.PwPolicyMgrImpl} and {@link org.apache.directory.fortress.core.impl.AuditMgrImpl}.
* There are more than 125 distinct test cases that kicked off from within this JUnit test wrapper.
* There are more than 150 distinct test cases that kicked off from within this JUnit test wrapper.
* Fortress JUnit test phases in this file include:
* 1. Tear-down data (optional) - during this phase previously loaded test data is removed from directory.
* 2. Buildup data - add it back.
* 3. Interrogate data - entity and security policy review APIs.
* 4. Check data - runtime security rule evaluations.
* 4. Audit data - validate audit log coverage.
* <p>
* Note 1: Data is retained in LDAP directory after these tests run (assuming the client was able to connect
* Note: Data is retained in LDAP directory after these tests run (assuming the client was able to connect
* to the LDAP server).
* Note 2: To delete old test data, run the "FortressJUnitDeleteTest" test cases after success on main (if repeatable
* runs of this class are not desired).
* Note 3: On test first run, assertions will fail on the teardown phase (#1) as (presumably) prior test data does
* not exist. The tests
* are designed to recover on repeated runs if/when ldap data falls out of synch - BUT - if/when errors do occur
* during repeat of buildup phase,
* delete the old test data manually in directory before trying again.
*
* @author <a href="mailto:dev@directory.apache.org">Apache Directory Project</a>
*/

0 comments on commit 704fa35

Please sign in to comment.