Create testing plan

[mmccool]

Issue #117 is a bit too specific. What is needed is a plan outlining how a scripting API implementation is tested for conformance with the specification. This can be a simple .md file, and may or may not use the assertion extraction mechanism used for the TD spec. Also the definition of "feature" should be discussed; features are points of the implementation to be tested but may or may not map directly onto assertions in the text. They may also relate to (for example) each entry point in the API defined in the IDL.

[zolkis]

Do we plan something generic like https://github.com/web-platform-tests/wpt/ ?

[danielpeintner]

@egekorkan are there any plans to extend https://github.com/tum-esi/testbench with the support of testing scripting implementations?

i.e., based on a TD scripts could be generated.

[egekorkan]

There are currently no plans to generate a script that can be run but the requests to be sent are generated on the Servient. The responses are also reported in a test report.
If a script is needed to be generated, what should it test?
Currently, wot-testbench test only the Exposed Thing through its TD and the Thing could be programmed in different ways, not necessarily via Scripting API.

[relu91]

Call 04/12:

• @zolkis: testing is important in W3C, issue raised by a Chair, we just didn't have the bandwidth to work on this.
• @relu91 proposing to put low priority for now and reevaluate later
• @mmccool please let us know if you feel otherwise and we need to prioritize this work. Or feel free to expand your original idea.
• @ashimura remind that it is not necessary to note document. It relates to how we want to do testing in general in the working group.