14:17:56 <RRSAgent> RRSAgent has joined #wot-pf
14:17:56 <RRSAgent> logging to https://www.w3.org/2022/02/02-wot-pf-irc
14:18:00 <McCool__> fs: any objections to mar 14-18, given tight timing?
14:18:14 <McCool__> cris: might be out for a day, but not a problem
14:18:29 <McCool__> mm: not hearing any objections
14:18:34 <McCool__> fs: so the scheduling is done
14:19:34 <McCool__> topic: testing
14:19:38 <kaz> i/any objections/scribenick: McCool/
14:19:38 <kaz> i/any objections/topic: minutes/
14:19:38 <kaz> i/any objections/mm: note that our last discussion was to have testfest feb 28-mar 4, but main call resolution was mar 14-18/
14:19:38 <kaz> i/any objections/... will have to discuss if that is a problem we have to fix/
14:19:39 <kaz> i|any objections|fs: also need to look at details of testfest/plugfest|
14:19:44 <McCool__> fs: is feature freeze done for TD?
14:20:03 <kaz> q+
14:20:12 <kaz> ack k
14:20:15 <McCool__> mm: for both TD and Discovery, not completely, but "mostly"; enough to start with testing except for a few dangling issues
14:20:27 <McCool__> kaz: just to confirm, have minutes been approved?
14:20:40 <McCool__> fs: any objections?... hearing none, approved
14:20:51 <kaz> -> https://www.w3.org/2022/01/26-wot-pf-minutes.html Jan-26
14:23:34 <McCool__> topic: discovery testing
14:24:06 <McCool__> mm: still distracted with final assertions, but soon
14:24:20 <McCool__> ... had some test suites, but not yet integrated
14:26:00 <kaz> present+ Kaz_Ashimura, Fady_Salama, Cristiano_Aguzzi, Jack_Dickison, Kunihiko_Toumura, Michael_Lagally, Michael_McCool, Tomoaki_Mizushima
14:26:05 <kaz> chair: Fady
14:26:12 <McCool__> ... but really it's only the output files that need to be consistent; it's ok if there are multiple test suites
14:26:41 <cris> q+
14:26:55 <McCool__> topics: deliverable
14:27:08 <kaz> regrets+ Ege
14:27:34 <mlagally> mlagally has joined #wot-pf
14:27:43 <mlagally> q+
14:28:15 <McCool__> mm: suggest we focus on TD/TM and Discovery in this round
14:28:47 <McCool__> cris: tm testing is just a small modification of the existing TD tests, right?
14:28:57 <McCool__> fs: yes, that's right; working on it
14:29:06 <dezell> dezell has joined #wot-pf
14:29:27 <McCool__> cris: we also need some test cases
14:29:36 <McCool__> mm: there are some tm's checked in already
14:29:50 <dezell> present+ David_Ezell
14:30:02 <kaz> rrsagent, make log public
14:30:07 <kaz> rrsagent, draft minutes
14:30:07 <RRSAgent> I have made the request to generate https://www.w3.org/2022/02/02-wot-pf-minutes.html kaz
14:30:12 <McCool__> mm: also assuming TMs will be in same implementation report
14:30:49 <McCool__> ml: true that profile spec is still doing another round, but there are some things that are fully spec'd and can be tested
14:34:13 <McCool__> mm: so I think we probably could extend the assertion tester (JSON Schema + scripts), but need to identify the "frozen" assertions
14:34:27 <kaz> q+
14:35:41 <McCool__> ml: we can however set up the toolchain, etc. and get a first draft out
14:37:58 <kaz> ack c
14:37:59 <kaz> ack m
14:38:06 <McCool__> mm: to clarify, I have to run the report generator
14:38:25 <kaz> meeting: WoT Plugfest/Testing
14:38:32 <kaz> rrsagent, draft minutes
14:38:32 <RRSAgent> I have made the request to generate https://www.w3.org/2022/02/02-wot-pf-minutes.html kaz
14:38:45 <McCool__> ... but start by copy over wot-thing-description/testing
14:39:28 <kaz> i/note that our last/scribenick: kaz/
14:39:40 <kaz> i/not hearing any/scribenick: McCool__/
14:39:41 <kaz> q?
14:40:04 <McCool__> mm: also want to mention the description of implementation reports in architecture needs to be updated... right now only mentions the wot-td one, but in fact this round we will have several
14:43:17 <McCool__> mm: also we may have to re-think the directory structure, i.e. need multiple csv files merged for each implementation
14:43:33 <kaz> i/also we/kaz: as I already mentioned the other day, we should clarify which spec needs what information (=assertion tests which can be automatically checked, and manual tests which might require actual communication between exposer and consumer. we can do that based on the proposed directory structure on the GitHub but should have concrete guide for that./
14:43:41 <kaz> i/as I/scribenick: kaz/
14:43:53 <kaz> i/also we/scribenick: McCool__/
14:44:59 <McCool__> mm: I think we need a simple way to merge results that does not depend on the assertiontester, since we won't actually have TDs to check e.g. for Discovery
14:46:45 <McCool__> topic: logistics
14:46:55 <McCool__> mm: need to update readme
14:47:50 <McCool__> fs: ok, will fix
14:48:13 <McCool__> fs: aob?
14:48:26 <McCool__> ... seems is not, adjourn
14:48:31 <kaz> q?
14:48:33 <kaz> ack k
14:49:27 <kaz> [adjourned]
14:49:33 <kaz> rrsagent, draft minutes
14:49:33 <RRSAgent> I have made the request to generate https://www.w3.org/2022/02/02-wot-pf-minutes.html kaz
17:01:48 <sebastian> sebastian has joined #wot-pf
17:02:21 <Zakim> Zakim has left #wot-pf