14:06:45 RRSAgent has joined #wot-pf 14:06:45 logging to https://www.w3.org/2022/02/23-wot-pf-irc 14:07:22 meeting: WoT Plugfest/Testfest 14:08:34 ryuichi has joined #wot-pf 14:12:57 chair: Fady 14:13:12 Mizushima has joined #wot-pf 14:13:27 present+ Kaz_Ashimura, Michael_McCool, Ege_Korkan, Fady_Salama, Kunihiko_Toumura, Michael_Lagally, Tomoaki_Mizushima 14:13:44 topic: minutes 14:13:56 https://www.w3.org/2022/02/16-wot-pf-minutes.html 14:14:57 scribenick: McCool 14:15:03 s/https/-> https/ 14:15:10 s/html/html Feb-16/ 14:15:18 present+ Ryuichi_Matsukura 14:15:22 fs: any objections? 14:15:28 ... no, will publish 14:16:07 fs: agenda topics, updates 14:16:13 mm: testing plan 14:16:42 agenda: https://www.w3.org/WoT/IG/wiki/PlugFest_WebConf#Agenda_23.02.2022 14:16:45 topic: updates 14:16:54 i/agenda topics/topic: Agenda/ 14:17:15 fs: have updated README under events/2022.03.Online 14:19:04 rrsagent, make log public 14:19:08 rrsagent, draft minutes 14:19:08 I have made the request to generate https://www.w3.org/2022/02/23-wot-pf-minutes.html kaz 14:19:24 i/mm: testing/topic: Testing plan/ 14:19:37 mm: overlap; want to know where testing plans should go 14:21:20 .. propose putting somewhere global, like wot-testing/planning/TD/test-plan.md 14:21:25 s/topic: Testing plan// 14:22:10 i/overlap/(discussion about the wot-testing repo's structure for the upcoming Testfest/ 14:22:48 .. suggest for now we just create empty files, link to them from README for testfest event 14:23:27 .. I can take the action to make a PR to do this 14:23:32 q+ 14:24:12 kaz: might make sense for Michael, Fady, etc. to have more discussion about template offline 14:24:50 topic: templates 14:24:54 ack k 14:25:00 kaz: would be useful to do offline and have PRs to discuss 14:25:55 fs: have one for scenarios 14:26:05 mm: would be useful to have one to describe implementations 14:26:13 ... testing plan as mentioned above 14:27:02 ... there is also an existing template for implementations 14:28:10 fs: can use events/templates 14:28:20 mm: not perfect, but I am ok with that 14:31:53 mm: will have to track it down, see PR under wot-architecture 14:33:35 ... will create a PR to get this organized... 14:37:25 ... also need to capture the discussion about the Conexxus demo as a plugfest scenario 14:37:29 topic: tools 14:37:45 fs: still working on updating assertion tester, hope to finish by next week 14:38:04 ... for TMs and TDs 14:38:18 ... so will handle TMs, and also new assertions for new TD spec 14:38:42 ... rather than autodetect, will require specification of what to do 14:39:39 https://github.com/thingweb/thingweb-playground/pull/224 14:39:59 ... in particular, don't want to misinterpret a missing @type for a TM as a TD; is in fact an error 14:41:31 ... 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 14:42:41 ege: suggest we delete that link to sub-repos and just have instructions 14:43:43 ... or rather, a sub-directory with a package.json so npm install will do the right thing 14:46:01 mm: other tools also 14:46:31 ... some tools, and some deliverables need "live" testing 14:47:01 ... eg security testing (eg fuzz testing for WoT TestBench) needs live instances 14:50:05 ... and I think doing something is infinitely better than nothing 14:51:16 ... for fuzz testing, may want to identify devices for which random input data is problematic 14:52:21 mm: maybe for now we can just focus on a few devices and get the process down for live and security testing 14:54:30 [adjourned] 14:54:35 rrsagent, draft minutes 14:54:35 I have made the request to generate https://www.w3.org/2022/02/23-wot-pf-minutes.html kaz 15:03:58 Mizushima has left #wot-pf 16:38:35 Zakim has left #wot-pf