![]() Need to learn how to use a host to properly exercise their plugin. Sticking to this smaller set of tests mean that the plugin authors don't Telling you if you implemented it right by _your_ business logic. "have I implemented my plugin right _by the API contract_?" - they're ![]() Resultant tests even address the main purpose of this suite, which is This is kind of pointless and can be more fluently expressedĪs standard test cases written by the manager author. We settled on the latter, as the former is basically making a meta testįramework. Of the semantics of the API contract and its invocation. Focus solely on the areas of the API that require specific knowledge That allowed you to define n number of invocations with different One was to parameterise some more generalised tests for each method To the methods, not the API contract itself. Should cover includes results that are very specific to the _inputs_ The `apiComplianceSuite` quickly highlighted that it's not easy toĭefine what should go in that suite. This will beĮxtended over time to cover the full interface as we developer the ![]() `identifier`, `displayName`, `info` and `managementPolicy`. We are building this in thin vertical slices to better facilitate OpenAssetIO#96.Ĭonsequently, this version has minimal coverage of the bootstrap methods Implementation of any given `ManagerInterface` implementation. Adds a test harness that can be used to validate the
0 Comments
Leave a Reply. |