Variable indirection allow another level of abstraction in using variables to modularize tests. A simple example is to have a group of similarly name variables and the use of another variable to control the actual test values used. Example: $StudentCN1="jstudent" $StudentCX1="ou=students,o=school" $StaffCN1="rstaff" $StaffCX1="ou=staff,o=school" You could define the test user, for one test pass by setting $Utype equal ...more »
Add an action that can take a named snapshot of an object state and another one that can restore the snapshotted state
Get the QA team that validates drivers for each release to use Validator, and release the basic set of tests that exersize the driver completely.
An On Failure action could potentially be useful.
For example: Run Cleanup.
Echo a message.
Maybe even start a workflow to go do some cleanup/notification/whatever
There are test suites that show off the various connectors. However, each driver NetIQ ships should have an Add On Package that has a DirXML-Resource with a text/json or maybe json/validator DirXML-ContentType that stores the test suite, Then just as you can read the connectors out of the IDV, also look for DirXMl-Resources whose DirXML-ContentType is validator/json and read them back and import the test suite. Buffer ...more »
Implement LDAP query function and store the query result in a multi-valued variable.
- Allow the stored format to be JSON, delimited text, xml.
- Allow max number of results to be variable (1...1000 or more)
It would be great to have an action that can get/convert CTIME and set to a variable. Ideally, this would mimic functionality of the Time noun and Convert Time verb that are supported by the engine. I realize you could accomplish this with scripts and the Execute connector, but it would be nice to have the functionality built-in to Validator.
Hey Guys! I'd like to be able to 'disable' actions for an entire connection - that would let me build integration tests (Say and HR JDBC driver to the Vault with AD and eDir drivers downstream) and run the same test suite as a Unit Test by disabling some connections (so I would disable the JDBC HR connection and eDir connections to unit test the AD driver - I would leave the connections to the ID Vault and AD domain active. ...more »
I was struggling to figure out why I could not approve a request with the UserApp connector. This was the error I would get: java.lang.AssertionError: java.lang.Exception: No task for this process/user while executing action method approveRequest. After using tcptunnel.sh to view the getWorkEntries SOAP call that Validator is making, it became apparent that the Recipient FDN is actually the addressee, and that the Process ...more »
Adding a RegEx Matcher to every Action would allow us to override the default behavior (if desired) of an action so we could evaluate the result message (eg thrown exception) to determine the pass/fail status of that action rather than assuming that all errors are "failed tests". This essentially would allow every action to also function as a true assert, instead of just adopting the default interpretation of the developer ...more »
It is not clear how you could read a value from AD, apply some simple math (such as UAC = UAC | 2 to disable an account)
For each test step in the report, include the description. This is what is seen when you collapse the test steps.