PR 27

PR 27 -nodegen population scripts

scribenick: kaz

McCool Nodegen population script

scribenick: Ege

McCool: This creates nodes in Node-RED based on the TDs of the repo

scribenick: kaz

McCool: Toumura-san, can you capture the screen, etc.?

Toumura: would put that tomorrow

scribenick: Ege

Ege: would be nice to watch the repo and generate nodes automatically

McCool: merging this PR

PR 16

PR 16 - validation scripts

McCool: I am working on the validation scripts but I decided to separate the implementation report

McCool: not having id also causes a problem on documenting the validation results

<kaz> validate.sh on McCool's repo

<inserted> scribenick: kaz

McCool: seems there is a bug

Ege: can you open an issue about that?

McCool: will do

Ege: choose manual or not to be done by the playground?

McCool: if you go to the AssertionTester...

AssertionTester

<inserted> scribenick: Ege

McCool: almost ready to merge this PR 16

<inserted> scribenick: kaz

McCool: need to see the possible impacts to the other PRs

<inserted> scribenick: Ege

McCool: Once PR 16 is merged, some files will be moved around
... so it can break other PRs
... you can use the manual.csv as a template

Kaz: Until when should the other participants fill the csv file? Also we need to copy the manual on how to do that from the previous page to this page.

McCool: Yes, I would like other participants to fill this

<inserted> scribenick: kaz

Kaz: ok, in that case, let's ask all the participants here to provide CSVs as well as TDs by tomorrow

McCool: yes

LinkSmart directory population

<inserted> scribenick: Ege

McCool: Directory population, any progress on this

Farshid: Yes, I have fixed some small things
... should I put it in the testing repository?

<kaz> SmartLink repo (in sync with the wot-testing repo)

<McCool> https://github.com/mmccool/wot-testing/tree/update-validation/tools

<inserted> scribenick: kaz

(farshid will create an issue on the wot-testing repo about his findings)

McCool: note that for the implementation report, the count is based on the same code-basis
... though one company may provide more than one TD
... Toumura-san, do you think you could do the demo on nodegen population tomorrow?
... would be great if it's possible

Toumura: will try

Introducing WADE

<Ege> https://github.com/w3c/wot-testing/tree/master/tools WADE tool

<Ege> https://github.com/tum-esi/wade

Ege: works with the TDs
... you can paste TDs directly
... or load them
... and then specify protocols
... then choose, properties, actions events
... and get results on the right side
... some TD like Oracle's blue pump requires additional credentials
... you can use CoAP as well
... (choose "TUM-CoAP16")
... can see the response time as well

WADE repo on the TUM side

Kaz: what is the "results" here?

Ege: the WADE tool is a consumer and processed the TD

Kaz: ok
... and the turn-around time is calculated based on the clock on the client side?

Ege: right

McCool: question about the random string
... would be good for actual usage too

Miguel: (shows W-ADE Tests for all non-VPN Things)
... actions don't work for the Oracle devices

Lagally:: what do you mean by "don't work" here?

Miguel: can get properties
... but when try actions, e.g., value: true
... get an error

Kaz: caused by the authentication level?

Lagally:: yeah

Daniel: I also tried to connect with the Oracle devices, but got no errors...

Lagally:: we should check what's happening a bit more

Ege: might need some more work for WADE

Kaz: yeah, let's look into the details and clarify what is the cause
... maybe a bug of WADE but might be some issue with network configuration or the device side

Miguel: (shows the TUM coffee machine next)

McCool: you can capture your screenshot for the description

Miguel: ok

Next steps

McCool: start to think of outcomes
... would say it would be great to have screen captures
... and also you can create an issue about your finding

Kaz: people should record not only the "success" side but also the "failure" side :)

McCool: right, the problem findings are useful
... it would be nice to have issues captured for further discussions
... and then any plans in your mind?
... e.g., interoperability data file
... maybe the node-red stuff
... Toumura-san, maybe you might want to collect interoperability tests as well
... and reflect the results to nodegen.csv

<McCool> https://github.com/w3c/wot-testing/tree/master/events/2020.06.Online/data/interop

McCool: TUM guys are also encouraged to work on WADE for that purpose
... hope we can capture some data for interoperability as well
... btw, wondering about the AWS VPN service
... possible to continue to use it for a while?

Kaz: let me check with the W3C System Team

McCool: ok
... (checking the network configuration diagram)

diagram on README.md

McCool: tx for maintaining it, Toumura-san
... let's continue the discussion tomorrow!

[adjourned]