Validator

Add Variable Indirection

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 »

Voting

3 votes

Validator

Ability to Get/Convert CTIME and Set to Variable

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.

Voting

3 votes

Validator

Disable Tests/actions by Connection

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 »

Voting

2 votes

Validator

Change UserApp 'Approve Request' Labels

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 »

Voting

2 votes
(@tnosredna)

Validator

Add RegEx Matcher to Every Action Allows Negative Testing

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 »

Voting

2 votes
(@geoffc)

Validator

LDAP Browser - Filter - Allow Subtree/Filter

LDAP Browser for searching for users, Apply Filter.
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 »

Voting

2 votes
(@rbrunold)

Validator

Add support for ldap controls

LDAP connections to server support different types of controls. Eg. there is a edirectroy control for supporting simple passwords via LDAP:

'2.16.840.1.113719.1.27.101.5': ('2.16.840.1.113719.1.27.101.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 »

Voting

2 votes
(@rbrunold)

Validator

Better support SAP iDoc based tests

We have a SAP connection in our IDM environment which receives data from human resources via the SAP file format iDoc.
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 »

Voting

2 votes

Validator

Allow variables to be used in Connection field

Enabling a variable value to point to a connection, would allow easier development of modularity in templates and tests.

The use case I have involves multiple eDirectory connectors with in a single system. A variable change to the connection name in a common template would allow a single template to be used for similar tests in each of the different eDirectory trees.

Currently, the only way to achieve this easy reuse... more »

Voting

1 vote