tum-esi / testbench Goto Github PK

If the counter.js script is tested, there is no request or response schema generated. Since this is one of the first things people can run as a servient, it should work

Travis cannot be used anymore and we are using gh actions everywhere. We should transition there.

Coming from #48 (comment)

We should use td types for more typeful ts code.

Currently, only HTTP, CoAP, MQTT and File are added but we should simply add everything in nodewot.

The readme should mention what cannot be tested at the moment. Some examples:

• observable properties
• events
• adapting to protocol bindings

Currently, all possible bindings are added to the servient but they should depend on the TuT TD. A separate client-side servient should be generated in the initiate step and deleted after the test.

The feature to remove protocol clients have been implemented in node-wot. Once it is released to npm, we should bring it here.

https://github.com/tum-ei-esi/testbench/blob/f32b3039459ae86694a5b85a5608131c8515ec6b/testing-files/perfectThing.js#L7

Currently, even with #41, we are not on the latest node-wot.

In places like

The table under the header Example Usage and then Quick Method with Default Configuration, 2.i has a row with key url and the corresponding value starts with ttp:// whereas it should be http://.
@egekorkan

node-wot needs to be configured like in this issue to be able to use security keys. If this is not implemented, at least the test-bench should stop and display a message.

wot-servient.conf.json is missing which obliges node-wot to use the default configuration, which uses port 8080. A conf like this is required:

{ "servient": { "scriptDir": ".", "scriptAction": false },
"http": { "port": 8081, "selfSigned": false } }

there is no input data in the action so there should be no need for an empty body right? Maybe need to check the protocol bindings and comment back on the issue