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 »
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.1137126.96.36.199.5': ('2.16.840.1.1137188.8.131.52.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 »
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.
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 »
To make validator tests more maintainable, it would be nice if one could reference other sets of variables/connectors or templates from a suite.
It will be easier to 'divide and conquer' testing if some common parts could be reused instead of having to copy/paste between suites.
We would like to put quite a lot of information in variables. It would simplify the overview if there was a built in namespace/grouping functionality. This would make it possible to introduce folding for each namespace/Group.
In the UI one could unfold only the section one is interested in.
Add a parameter to select a specific test in a suite file to run from command line.
I would like to create a suite with two tests, one basic for Swift verification and one for mor thorough tests.
Then I want to run these from command line.
It will be a maintenence problem to put these tests in diffrent suite files, since they will be based on the same set of templates.
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.
Allow looping over values in a variable.
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)
Since many workflows are started automatically, it would be helpful In the UserApp connector if there was a way to get a list of workflow approvals pending for a particular user. This would allow us to know if the workflow was automatically started correctly.
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.
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.
Please comment with your ideas.
When developing a test, often I find I want to just re-run one specific action. Could we get a Run icon, inside a test, so that we could run just an "Assert" or a "Create Object" instead of having to run through the entire test. Often I find I disable all the other stuff just to run this one item again and again. Only run the tick box selected items if the button is pressed. This would go in the toolbar inside... more »