Meeting minutes
Minutes review of Testfest
Testfest Day 1
<kaz> Day 1
McCool: We have reviewed the minutes of the testing calls
McCool: we have merged many PRs
McCool: let's publish day 1 then
Testfest Day 2
<kaz> Day 2
McCool: some small fixes but we can publish otherwise
Testfest Day 3
<kaz> Day 3
McCool: we looked at a bunch of PRs
McCool: some small fix on needing to add the word "twice" after "count"
Testfest Day 4
<kaz> Day 4
McCool: some small fixes
McCool: hearing no objections, we can publish
McCool: with this we are done with the testfest minutes
Results
Discovery
<McCool> wot-discovery PR 447 - Update Implementation Report - Dec 2022 Testfest
<kaz> Implementation Report
McCool: we see fail at automatic results, a bit concerning
McCool: we have at risk items at discoverer
McCool: We have a dependency on two assertions
McCool: can we split an assertion to two?
<kaz> Kaz: do you want to change the spec text itself for this change after CR transition?
Kaz: we would need to consult with PLH if it's possible to add this kind of big change even for clarification
McCool: (creates an issue)
<McCool> https://
McCool: we should move the did part as at risk since we are doing it wrong
Kaz: we need to wait for implementation experience from developers if we publish a CR now
Kaz: The question here is whether we really think that the changes are editorial or not.
kaz: please talk with PLH before CR publication
TD results
Ege: I have fixed two bugs in playground
Kaz: sorry but as the starting point, probably we need to validate the testing tool itself a bit more seriously again given the situation. At least, we should look into what's happening with the result data for the features at-risk.
Architecture
Kaz: maybe we need to provide some clarification on how to deal with manual tests to the implementers, because lacking implementations for basic features like interface abstraction is really odd
[adjourned]