Provide sample tests that cover default driver configs
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.
Store test suite in attribute, deliver in Package.
If test coverage for default driver config can be developed, consider a mode of storing the Validator config in an eDir object (DirXML-Resource class, with DirXML-ContentType=mime/Validator-test-suite) so that when you import drivers from Vault in Validator, you also get a default test suite. Would allow developers to ship drivers with test suites included.
Make test suite a Designer Package for drivers
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 »
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 »