Meeting minutes
Minutes review
<kaz> Mar-2
Fady: any objections to the minutes?
<kaz> none; approved
discovery testing plan
McCool: toumura-san, is your mdns explorer in the node-red available?
Toumura: yes
oracle plugfest TDs
<kaz> Oracle TDs
https://
Lagally: our Things are behind basic auth
McCool: you should use td or td.jsonld as suffix, fady and ege, what do we check?
Ege: the validation script in here uses td.jsonld
Fady: playground looks for .jsonld or .json
McCool: we should use the implementation based directory structure
Lagally: we have these digital twin simulators such as blue pump, connected car
McCool: are these testfest or plugfest contributions, are you testing new features like events etc.
Lagally: can be considered testing contribution
Fady: we need information about the implementation the TD belongs to
McCool: the directory structure can be enough for that
McCool: should we copy over the old TDs
Ege: I would not do that in order to make sure to have correct context url
PRs
https://github.com/w3c/wot-testing/pull/217
Fady: we can merge these rightaway
https://github.com/w3c/wot-testing/pull/216
Fady: should we put directories for organizations under the implementation
McCool: before we used to have name of the org in the name of the TD
Lagally: If you want to have access to Oracle devices, please send me an email
Sebastian: how is this working with TMs?
McCool: we can have TMs under the TD folder
PR 218
<kaz> PR 218 - Improve testing plan
Ege: I have added definition of types of testing, put the tools per type of testing and deliverable
McCool: we should have a csv or some annotation that says that a thing can be tested with testbench or behavioral test
Ege: I can do behavior testing in the next plugfest
McCool: it would be nice to have open api document of all of them
Ege: that can be done but I do not need it for testbench
PR 215
<kaz> PR 215 - Oracle plugfest tooling
<kaz> merged
<kaz> [adjourned]