Meeting minutes
Agenda
McCool: should work on implementation test metadata
Minutes
McCool: relatively short
meeting
… clarification for discovery
… any problems?
(none; approved)
Testfest planning
McCool: let's start with TD
TD area within the wot-testing repo
report template within the wot-thing-description repo
McCool: (discuss the requirements for implementations)
[[
Each implementation represents a working system
that either exposes or consumes at least one WoT Thing Description.
]]
McCool: would have two implementations for both producer and consumer
Ege: need update for the implementation result table as well
PRs
PR 125 - fix(json): Fix json files to be json parsed
McCool: (merges the PR)
Test report metadata
McCool: (creates a new
branch, "test-report-metadata")
… (copies the content from
wot-thing-description/testing to the test-report-metadata branch of
the wot-testing repo (locally copied on McCool's PC))
… (adds edits to the
testing/inputs/templates/report.html file"
… any updates for the template in
general?
Kaz: implementation reports are generated by the WGs and no general templates
McCool: ok
… (continue to add updates to the
report.html)
… (goes through the file)
… (changes the criteria section)
[[
Our goal is that all required features will have at least two implementations and all optional features will have at least one implementation.
]]
(some discussion on how to track the resulted behaviors)
McCool: (updates the "5.
Implementation Report requirements" section)
… (moves ahead to "6. Systems"
section)
… question about "servers" vs "clients". can be
converted to "producers" vs "consumers" within the WoT
context
… (then "7. Security")
McCool: (revisits the issue
on "servers" and "clients")
… producers should be assertion
testers
… one consumer with multiple producers
… need manual assertions
Ege: is there any feature used by both the sides?
McCool: maybe we could
split the Pass/Fail column into Consumer Pass/Fail and Producer
Pass/Fail
… so could have two separate result columns, one
for Consumers and another for Producers
… maybe we should have two separate
tables
… one for data itself and another for
behavior
(we're getting out of time...)
Kaz: so will you push the updated report.html to the wot-testing repo?
McCool: yes, will do now
[adjourned]