Meeting minutes
minutes
fs: any objections?
… no, will publish
Agenda
fs: agenda topics, updates
mm: testing plan
updates
fs: have updated README under events/2022.03.Online
<kaz> (discussion about the wot-testing repo's structure for the upcoming Testfest
mm: overlap; want to know where testing plans should go
… propose putting somewhere global, like wot-testing/planning/TD/test-plan.md
… suggest for now we just create empty files, link to them from README for testfest event
… I can take the action to make a PR to do this
kaz: might make sense for Michael, Fady, etc. to have more discussion about template offline
templates
kaz: would be useful to do offline and have PRs to discuss
fs: have one for scenarios
mm: would be useful to have one to describe implementations
… testing plan as mentioned above
… there is also an existing template for implementations
fs: can use events/templates
mm: not perfect, but I am ok with that
mm: will have to track it down, see PR under wot-architecture
… will create a PR to get this organized...
… also need to capture the discussion about the Conexxus demo as a plugfest scenario
tools
fs: still working on updating assertion tester, hope to finish by next week
… for TMs and TDs
… so will handle TMs, and also new assertions for new TD spec
… rather than autodetect, will require specification of what to do
<Ege> https://
fs: in particular, don't want to misinterpret a missing @type for a TM as a TD; is in fact an error
… do we need to update the sub-repo link, or (since this was only used by my script, which is going away) just instructions on how to pick up the correct
ege: suggest we delete that link to sub-repos and just have instructions
… or rather, a sub-directory with a package.json so npm install will do the right thing
mm: other tools also
… some tools, and some deliverables need "live" testing
… eg security testing (eg fuzz testing for WoT TestBench) needs live instances
… and I think doing something is infinitely better than nothing
… for fuzz testing, may want to identify devices for which random input data is problematic
mm: maybe for now we can just focus on a few devices and get the process down for live and security testing
<kaz> [adjourned]