When your action makes a change to object attributes, the prior values should be preserved, so that a new action could "undo" the change. You could either stack the prior values, or allow the undo to reference a specific change.
Add an action that can take a named snapshot of an object state and another one that can restore the snapshotted state
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)
Or it would be great to tie in new functionality into validator that would perform the Analyzer functionality. Compare values... more »
This idea came up in some discussions at Brainshare.
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.
If test coverage for default driver config can be developed, consider a mode of storing the Validator config in an eDir object (DirXML-Resource class, with DirXML-ContentType=mime/Validator-test-suite) so that when you import drivers from Vault in Validator, you also get a default test suite. Would allow developers to ship drivers with test suites included.
It seems like most "Assert ... Results Contains" tests support retries. The HTTP connector tests do not. That feature should be available across all assertion tests.
I know you can run "Use XPath and Set Variable", then do an assertion on that variable. However, "Assert XPath Results Contains" and "Assert XPath Results Not Contains" would be very useful, by which you could specify an Xpath expression and do an assertion all in one step.
Use case: I make a SOAP... more »
Ideally the command line could spit out the test results in JSON or some useful format that could be used as input to another process.
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
For each test step in the report, include the description. This is what is seen when you collapse the test steps.
I do not think we can do multivalued local variables, nor loop over them, but we need to
1) Ensure they are all deleted.
2) Ensure that at least 1 or more are created.
This seems like a new assertion of LDAP Filter returns, with sub options of:
0-n values... more »
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 »
We create users for testing different things. At one point we were getting an error on the creation so we had to back out the attributes one by one and then re-add. It would be a huge help to be able to just disable them. Same with if you are "Asserting attributes and Values in eDirectory" if you have several items here you can enable/disables items.