W3C home > Mailing lists > Public > public-wot-wg@w3.org > May 2018

[wot-test] minutes - 16 May 2018

From: Kazuyuki Ashimura <ashimura@w3.org>
Date: Mon, 21 May 2018 18:52:51 +0900
Message-ID: <CAJ8iq9U6XrLQ0JJe9QDrhbtVdJB_gmvFVCQQmi2wh33Ry60gpw@mail.gmail.com>
To: Public Web of Things IG <public-wot-ig@w3.org>, public-wot-wg@w3.org
available at:

also as text below.

Thanks a lot for taking the minutes, Michael Koster!




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

                               - DRAFT -

                                WoT Test

16 May 2018


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


          Michael_Koster, Michael_Lagally, Tomoaki_Mizushima,
          Toru_Kawaguchi, Ege_Korkan, Toru_Kawaguchi

          Matthias, Kajimoto, Dave, Kaz




     * [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


   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
   ... 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


   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
   ... 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
   ... probably only need to test some specific protocol
   ... 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
   ... 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

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:27:49 UTC