Adding extra logic into the test cases depending on the value of a variable.
Make it possible to lock each group of actions from dragging to change order. I find it's very easy to accidentally change the order of actions. It would be nice to have the option to lock them in place.
It should be possible to host Validator as a shared, central web-service,
but this requires a proper user athentication and authorisation, e.g. via LDAP or SAML.
Replay test(s) n number of times
This will prompt a user to add a value and then store it in a variable so it can be used later in the text.
It should be possible to set the association status of an associated object to test migration and sync events. Validating a status is already possible by checking “DirXML-Associations contain ‘Driver-DN#Assoc-Status#’”, migrating not associated objects by “Add DirXML-Associations ‘Driver-DN#4#’, but it’s not possible to change the status of an associated objects. Maybe, implementing Regexp + a replace feature could provide... more »
There are test suites that show off the various connectors. However, each driver NetIQ ships should have an Add On Package that has a DirXML-Resource with a text/json or maybe json/validator DirXML-ContentType that stores the test suite, 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 »
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 »
In addition to the User App start workflow action, it would be great to have actions to add and remove resources. Sometimes in testing I need to directly assign or revoke a resource, without the need to start a custom workflow.
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.
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
We have a case, where we have Sendmail objects that have an attribute, serialNumber, we can query on via LDAP. This would return a list of 1-N objects back. 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 »
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)
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 »