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.
Instead of literal strings we use GCVs to deal with environment specific values in policy. Being able to import existing driver/driverset GCVs as variables would eliminate the step to manually redo them in validator.
Please comment with your ideas.
The new lock for actions is well done and a great improvement. We need the exact same thing for the test themselves. I have many test files with huge lists and the same issue that causes them to loose there order because of the drag and drop functionality. Please add the same lock that is on items to tests.
Allow looping over values in a variable.
It could be nice if a template could take arugments like the following.
Simple example but a really powerful tool. Reuse of templates and they become functions instead.
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 »
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.
We use git for version control on our test cases. But Validator makes this a bit cumbersome because it stores the actual test case logic combined with state information in one file. Bot layout state (if a group is expanded or not) and variable values should be stored separately.
The addition of a LDAP login is nice. It would be helpful if the users did not need DN. I think the way to do this is a bind user that could search for the user context.
Add subtree search for filter.
When searching for a user, say in Create User, where you can import values from an object, as you browse, if you have a deep structure then you are scrolling up and down ALOT to find the parent container, then scroll to the top, click Apply Filter, and then scroll back down.
This would be simpler if:
1) Subtree searching was an option/default/config.... more »
'2.16.840.1.113722.214.171.124.5': ('2.16.840.1.1137126.96.36.199.5', OID_CONTROL, 'Simple password', 'NOVELL'),
Other controls are available for getting a server side sorted list back from LDAP searches, using persistent searches and so on.
Please add a option for LDAP connections... more »
That is a standardized format which should be supported by Validator.
There is just a text file connector, which allows simple text files, but iDocs have a very difficult format. Long lines and so on.
The default text file connector is not sufficient for this.
Please either extend the current text file... more »