Validator Community Browse Popular ideas

IDM Validator 1.2
UserApplication Connector
User Interface, etc.

After setting up a UserApp connection and getting PRDs tested for the first time a few things would really help make this much simpler.

First, allow browsing to the PRD. Designer doesn't provide the DN anywhere convenient, and even finding the CN can be a challenge. Since browsing the vault is already an option (for a different type of connection, of... more »

The current validator runs a dos batch file that starts the Java Process and all the magic happens. The issue I have is it is easy to accidentally close the DOS box and than you have a mess with the interface open and no process to preform the operations. There has been a user who has provided this as an add on yet each revision has broken it and I am not aware if you can still obtain this for the most recent versions.... 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 »

When you copy a function to a complimentary fuinction, for example, Copy an Add Object and change it to a Delete Object, the corresponding fields should be maintained. The DN from the add object should become the DN of the delete object (right now it puts the class name in when you do that).

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)

The Analyzer product seems to not be used much even though everybody that has access to the Advanced Edition has a license for it. It would be great to tie the existing connections that validator has and allow analyzer to take that connection information and connect to the various connections.

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.

The concept would be to be able to import ECMA scripts from drivers and then have those functions available in an Action for a validator test. So you could pass in variables to an ECMA/javascript script, get the result and assign it to another variable.

Additionally, we could just allow a javascript action so javascript could be included in any test.

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.

It would be nice to have actions that allow you to perform assertions on Xpath results without first setting a variable.

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