W3C

– DRAFT –
WoT Plugfest/Testing

30 March 2022

Attendees

Present
Cristiano_Aguzzi, Daniel_Peintner, Fady_Salama, Kaz_Ashimura, Kunihiko_Toumura, Michael_McCool, Ryuichi_Matsukura, Sebastian_Kaebisch, Tomoaki_Mizushima
Regrets
-
Chair
McCool/Fady
Scribe
kaz

Meeting minutes

Minutes

Mar-23

approved

Manual CSV

Fady: not sure what to do
… next week, will give a demo on how to do with Ege's help

McCool: 2 questions
… template updated?

Fady: that's my 2nd point here
… we need clearer pipeline
… things are always changing
… need to clarify which assertions are automatic and which are manual

McCool: that's the first issue
… 2nd issue is that manual assertions are not tested automatically

Kaz: not sure what we want to do today
… should clarify what is done during he March Testfest and what is not done yet first

Issue 280 - Testfest 2022-03 Followup

McCool: (shows the followup issue)

Kaz: yes, we should start with this followup issue

Fady: we still need some more PRs for manual CSVs

Kaz: so you both would like to start with the 5th point of manual CSVs for TD?

McCool: yeah

Kaz: do you mean manual CSVs for TD?

McCool: yeah
… manual CSVs for TD
… there was some confusion
… would like Fady and Ege to generate a list they're handling

Kaz: Fady, can you show the situation?

Fady: would like to wait until next week

McCool: would like to see the list of assertions we tested too

Kaz: in that case, what should be done today?

McCool: nothing really...

Kaz: in that case, can we quickly skim the other topics instead?

McCool: yeah
… we can try the 4th point
… "Implementation report drafts"
… structure of the wot-testing repo

Draft implementation report for TD

<McCool> https://github.com/w3c/wot-thing-description/pull/1451

<McCool> https://htmlpreview.github.io/?https://github.com/w3c/wot-thing-description/blob/5e9f15c8f62792c8ef8063620bbfa3fa98d521ed/testing/report11.html

McCool: rendered version above
… a lot of features passed
… we have 11 different directories
… gaps include JSON pointer
… need some example for that
… some weird corner cases there
… also some of the features should have more results
… like td-additionalExpectedResponse-contentType
… td-context-default-language-direction-script to be tracked down
… multi-language support

Kaz: after checking the results and the script, if there are any features missing implementations, we need to ask people to provide implementations for those features

McCool: right
… there a lot of missing implementations for Thing Model

Sebastian: can the tests already check TM features?
… kind of surprised with the current results...

McCool: yeah

Kaz: please check the script and the results directories again

McCool: yeah
… looks suspicious to me too
… then we have the section for manual assertions
… section 8.2
… need to check the results for that too

Draft implementation report for Architecture

McCool: (generates a rendered version locally)
… need to update the source files
… 11 results there
… some of them overlap

Kaz: because they use the same code base?

McCool: right
… also something add happening within the HTML
… look at that again
… (shows the text on implementations)

Kaz: those descriptions are imported from the testimonial texts. right?

McCool: yeah
… (shows wot-architecture/testing/inputs/impls/hitachi.html on his PC)
… need to move the content back to the wot-testing repo
… (then shows wot-testing/events/222.03.Online/Architecture/impls/ditto.html)
… will update the content

Draft implementation report for Discovery

McCool: have similar problem with generating the rendered version...
… (shows locally generated HTML)
… we do have 3 implementations
… need some work to clean the results
… 3 directory implementations already
… but missing implementations for clients

Kaz: maybe it would be better to split the result page into two parts, client and directory

McCool: yeah, that's true
… auto and manual are still kind of mixed up
… some of the features are new
… have not checked SPARQL features, etc.

Kaz: if you fix the script based on the TD results, it would be beneficial to the results of Architecture and Discovery too. right?

McCool: yeah, definitely

<McCool> file:///Users/mmccool/Downloads/report.html#automated_validation_results

Kaz: maybe it would make sense for you (McCool), Fady and Ege to have preparatory chat before the next call on April 6

McCool: could have some chat
… but Fady and Ege are understanding what they need to do

Kaz: yeah
… my point is get well-prepared before the next call :)

McCool: ok
… if we time, would try to update the results before hand
… let me capture the points within Issue 280

Issue 280 - Testfest 2022-03 Followup

McCool's comment on TODOs

McCool: Fady, do you have any additional topics in your mind?

(some more discussion on the TODOs)

McCool: people can provide updated TDs

Kaz: do you want people to submit updated TDs before the next Plugfest call or after the next call?

McCool: either is fine

[adjourned]

Minutes manually created (not a transcript), formatted by scribe.perl version 185 (Thu Dec 2 18:51:55 2021 UTC).