Closed kmohr-soprasteria closed 1 month ago
yaml schemas with examples.txt
The validator folder contains a data file. The standard datafile has a flat collection input list. For apps where there's e.g. only the mountName as input parameter this is fine. But the MWDI has also services, where other parameters are required (e.g. notification/subscription services).
Therefore it possibly would be nice to have another substructure per tested service containing input parameters for that specific service.
To check: how does MATR testcase collection handle e.g. the read-current-mac-table-from-device input? (There the caller must also provide requestor-info.)
These will be used to support testing. See examples in MATR or APTP repos (so far completeness simulator to test responses against schema).
Scope only on convenience services + link/linkport services. For other ressource paths see MDIP.