Problem description
The first version of the test plan covers very few logic of the current version of the API. As this was just the first version of an initial API it was not a requirement for the last meta-release
Expected action
In anticipation to a next version of this API it is convenient to design a more complete test plan, with similar detail to what we have for other APIs in the Working Group. We should cover every possible response for every operation operation, and the events logic.
Additional context
This is expected to be part of a next meta-release, so versions in the test plan should be set to WIP, as we already have in main branch.
Problem description
The first version of the test plan covers very few logic of the current version of the API. As this was just the first version of an initial API it was not a requirement for the last meta-release
Expected action
In anticipation to a next version of this API it is convenient to design a more complete test plan, with similar detail to what we have for other APIs in the Working Group. We should cover every possible response for every operation operation, and the events logic.
Additional context
This is expected to be part of a next meta-release, so versions in the test plan should be set to WIP, as we already have in main branch.