This would allow us to test workflow GUIs and any other GUIs inside a browser.
Test grouping/folder feature (2-x layers) which have also the select/deselect "all tests below" function to get a better overview in complex test scenarios.
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
Adding extra logic into the test cases depending on the value of a variable.
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.
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:
You could define the test user, for one test pass by setting $Utype equal... more »
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 »
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.
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.
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.
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 »