[PlugFest/Testing] minutes - 26 May 2021

available at:
  https://www.w3.org/2021/05/26-wot-pf-minutes.html


also as text below.

Thanks,

Kazuyuki

---
   [1]W3C

      [1] https://www.w3.org/


                             – DRAFT –
                              WoT Testfest

26 May 2021

   [2]Agenda. [3]IRC log.

      [2] https://www.w3.org/WoT/IG/wiki/PlugFest_WebConf#Agenda_26.05.2021

      [3] https://www.w3.org/2021/05/26-wot-pf-irc


Attendees

   Present
          Ege_Korkan, Kaz_Ashimura, Kunihiko_Toumura,
          Michael_McCool, Tomoaki_Mizushima

   Regrets
          -

   Chair
          McCool

   Scribe
          kaz

Contents

    1. [4]Agenda
    2. [5]Minutes
    3. [6]Testfest planning
    4. [7]PRs
    5. [8]Test report metadata

Meeting minutes

  Agenda

   McCool: should work on implementation test metadata

  Minutes

   [9]May-19

      [9] https://www.w3.org/2021/05/19-wot-pf-minutes.html


   McCool: relatively short meeting
   … clarification for discovery
   … any problems?

   (none; approved)

  Testfest planning

   McCool: let's start with TD

   [10]TD area within the wot-testing repo

     [10] https://github.com/w3c/wot-testing/tree/main/events/2021.06.Online/TD


   [11]report template within the wot-thing-description repo

     [11] https://github.com/w3c/wot-thing-description/blob/main/testing/inputs/templates/report.html


   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

   [12]PR 125 - fix(json): Fix json files to be json parsed

     [12] https://github.com/w3c/wot-testing/pull/125


   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]


    Minutes manually created (not a transcript), formatted by
    [13]scribe.perl version 131 (Sat Apr 24 15:23:43 2021 UTC).

     [13] https://w3c.github.io/scribe2/scribedoc.html

Received on Monday, 12 July 2021 07:38:01 UTC