[wot-test] minutes - 16 May 2018

available at:
  https://www.w3.org/2018/05/16-wot-test-minutes.html

also as text below.

Thanks a lot for taking the minutes, Michael Koster!

Kazuyuki

---

   [1]W3C

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

                               - DRAFT -

                                WoT Test

16 May 2018

   [2]Agenda

      [2] https://www.w3.org/WoT/IG/wiki/Test_WebConf#Agenda_16_May_2018

Attendees

   Present
          Michael_Koster, Michael_Lagally, Tomoaki_Mizushima,
          Toru_Kawaguchi, Ege_Korkan, Toru_Kawaguchi

   Regrets
          Matthias, Kajimoto, Dave, Kaz

   Chair
          Michael_McCool

   Scribe
          Michael_Koster

Contents

     * [3]Topics
         1. [4]agenda
         2. [5]progress to plan
         3. [6]tools
         4. [7]the role of simulated devices in testing
     * [8]Summary of Action Items
     * [9]Summary of Resolutions
     __________________________________________________________

   <McCool> scribe: Michael_Koster

agenda

   McCool: review progress
   ... next step planning, extracting normative statements
   ... tooling (Ege will present TD Playground next week)
   ... online test systems
   ... mlagally presentation
   ... any other items?

progress to plan

   <McCool> [10]https://github.com/w3c/wot/tree/master/testing

     [10] https://github.com/w3c/wot/tree/master/testing

   McCool: at this point we should be extracting normative
   assertions
   ... there is good RFC2119 style markup in the documents now
   ... need to track normative assertions in a separate document
   to develop test cases for them
   ... assertions.md for example
   ... reference to the source document and what the statement is
   ... description of test case
   ... do this for TD and Scripting API documents
   ... (creating PR)

   [11]PR #137 in TD repository

     [11] https://github.com/w3c/wot-thing-description/pull/137

   Lagally: add a class column for MUST/MAY/SHOULD

   McCool: will also create a PR for Scripting API

tools

   Ege: TD Playground is based on a JSON Schema validator
   ... also generates test data for test instances

   McCool: what about min-max values and other constraints?

   Ege: thinking about default ranges with reasonable constraints

   McCool: for each interaction there could be constraints

   Ege: may need additional metadata
   ... this tool works with the FPWD version
   ... a student is adding events and updating the TD
   serialization version

   McCool: we also need a tool that can validate the Scripting API
   implementation
   ... maybe using webIDL
   ... TD validator is also needed

   Ege: TD Playground validates TDs and tests things against TDs

   McCool: we also need to test additional implementations of the
   Scripting API

   Ege: the tools only test HTTP and CoAP
   ... protocol bindings can be "interesting"

   McCool: maybe we can't test all possible protocols
   ... and payloads
   ... we are required to validate the testability of the
   specification
   ... probably only need to test some specific protocol
   combinations
   ... we are also required to do penetration testing

the role of simulated devices in testing

   Lagally: simulated devices provided by the Oracle simulator
   using a Raspberry Pi

   McCool: system level simulation is needed

   Lagally: presents the Oracle simulator and IoT cloud service

   McCool: will look into extracting the normative statements

   Lagally: the simulator could provide some online plugfest
   components
   ... still missing an online node-wot instance
   ... adjourn

Summary of Action Items

Summary of Resolutions

   [End of minutes]
     __________________________________________________________


    Minutes formatted by David Booth's [12]scribe.perl version
    1.152 ([13]CVS log)
    $Date: 2018/05/21 09:49:55 $

     [12] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
     [13] http://dev.w3.org/cvsweb/2002/scribe/

Received on Monday, 21 May 2018 09:54:01 UTC