PlugFest WebConf/2019

Agenda 11.09.2019

• Online Plugfest results
  • fixed hangout information
  • Roundtable: Which devices, which test cases to prioritize, additional test cases?
  • Simple communication test
  • Test Scenarios
    • Smart House
    • Industrial integration

• F2F and Plugfest Logistics
  • Fukuoka demo/break-out setup
    • what scenarios (including which devices/apps) for which sessions?
    • what to check today, Sunday and Tuesday?
  • Demo logistics
  • 16-20 September, Fukuoka

• Demo preparation on Sunday, Sep. 15
  • Plugfest preparation registration, please!
  • starting time is 1pm at Fujitsu
  • network logistics (ordinary wifi for Internet connection and a mobile router by NHK)

Agenda 10.09.2019

• Online Plugfest
  • Roundtable: Which devices, which test cases to prioritize, additional test cases?
  • Simple communication test
  • Test Scenarios
    • Smart House
    • Industrial integration
    • Others?

• F2F and Plugfest Logistics
  • Fukuoka demo/break-out setup

• • 16-20 September, Fukuoka
  • Demo logistics
  • Plugfest preparation registration

Agenda 4.09.2019

• Online Plugfest
  • Doodle for time slot

Closing doodle, decided on time slot Tuesday, Sept 10th, 9am-11am CDT, 4pm-6pm JST (possibly 1 hour more, if needed)

• PRs

• F2F and Plugfest Logistics
  • 16-20 September, Fukuoka
  • Demo logistics
  • Plugfest preparation registration

Agenda 28.08.2019

• Online Plugfest
  • Doodle for new date

• PRs

• F2F and Plugfest Logistics
  • 16-20 September, Fukuoka
  • Demo logistics
  • Plugfest preparation registration

Agenda 14.08.2019

• Online Plugfest
  • Doodle for new date

• TPAC Demo Planning
  • https://github.com/w3c/wot/tree/master/plugfest/2019-tpac-fukuoka

• PRs

• Demo Logistics
  • https://www.w3.org/WoT/IG/wiki/F2F_meeting,_16-20_September_2019,_Fukuoka,_Japan#Demo_preparation_.2814-15_or_16-17_Sep_2019.29

• Next F2F(Singapore)
  • 13-17 November, Singapore

Agenda 24.07.2019

• Demo goals
  • Interoperability across multiple companies
• Demo Planning
  • https://github.com/w3c/wot/tree/master/plugfest/2019-tpac-fukuoka
• PRs
• Demo Logistics
  • https://www.w3.org/WoT/IG/wiki/F2F_meeting,_16-20_September_2019,_Fukuoka,_Japan#Demo_preparation_.2814-15_or_16-17_Sep_2019.29

Agenda 17.07.2019

• Demo goals
  • Interoperability across multiple companies
• Demo Planning
  • https://github.com/w3c/wot/tree/master/plugfest/2019-tpac-fukuoka
• PRs
• Scenarios
  • Starting point: Munich workshop demos: https://github.com/w3c/wot/blob/master/workshop/ws2/demos-2019-Munich/demos/README.md
• Demo Logistics
  • https://www.w3.org/WoT/IG/wiki/F2F_meeting,_16-20_September_2019,_Fukuoka,_Japan#Demo_preparation_.2814-15_or_16-17_Sep_2019.29

Agenda 10.07.2019

• Demo goals
  • Interoperability across multiple companies
• Consolidate Scenarios

Agenda 29.05.2019

• Demo preparation
  • Review of: https://github.com/w3c/wot/blob/master/workshop/ws2/demos-2019-Munich/README.md
  • PRs
  • Logistics
• Testing

Agenda 22.05.2019

• Demo preparation
  • Review of: https://github.com/w3c/wot/blob/master/workshop/ws2/demos-2019-Munich/README.md
  • Preparation for next week's dry run - WebEx, Hangouts, ...
  • Mozilla / WoT interworking
  • AOB

Agenda 08.05.2019

• At-risk updates in TD spec
• Directory change for test TDs
  • https://github.com/w3c/wot/blob/master/testing/tests/2019-05/
• Schedule

Agenda 01.05.2019

Cancelled due to holiday.

Agenda 24.04.2019

• Testing
  • Need to rerun IR report generator with AssertionTester fixes
    • https://github.com/w3c/wot-thing-description/issues/388
  • Recent changes to the TD spec may need new tests:
    • @context is now mandatory
    • Time/date fields should be checked using a pattern check
• Demos at June Workshop

Agenda 06.03.2019

• TD Implementation report update
  • Vocab ids changed to have context
  • Massive update to AssertionTester
  • Still some gaps
• Security
  • Penetration Testing
• Next steps
  • Ege will review AssertionTester schemas and fill gaps
  • McCool to update wot manual.csv and mail it around; update atrisk; also identify assertions that don't have tests yet
  • Aim for updated Implementation Report by Friday, final version for TAG by Monday
  • McCool working on documenting Intel systems for pentest planning (to be discussed in Security call on Monday)
• AOB

Agenda 13.02.2019

• Open Geospatial
• Uniqueness testing
  • What keys need to be unique and how can we test?
• How to tracking issues with testing
• Updates to IR
  • Assertions removed, general cleanup

Agenda 23.01.2019

• TestFest Logistics
  • Scheduling
  • Demo organization (eg for OpenDay)
• Assertions and Implementation Report Updates
  • Default values removed from IR table
  • Shadowed assertions added
  • Duplicate assertions (and IDs!) from tables
  • Behavioral assertion PR
• Tooling
  • Update to Playground
• Node-Wot update
  • 90% done, still issues with readall, security coverage
• Data Collection
  • Need to document CLI tool usage
  • Move mergeresults.js to playground repo
  • Need to update templates.csv - fix shadows, add behavioral
  • Examples directory
• Security Testing
  • Testing plan WIP
  • Penetration testing planned during F2F - failsafe devices, please!
• Other

Agenda 16.01.2019

• Definitions
  • What is an implementation?
  • Need to clairify status of "manual TDs + legacy devices"
• Logistics
• Workflow
  • https://github.com/egekorkan/wot/tree/master/testfest/2019-02-princeton
  • Participant roles
  • How to test
  • How to record results
• Validation Tools
  • Playground (JSON Schema validation)
  • Network Tool
• Data Collection
  • TD Implementation Report Tooling
  • TDs w/ CSV and directory structure
  • Implementation Descriptions
• Deliverables
  • Implementation Report
  • Interoperability Testing
  • Security Testing
• Process for Assertion Modification
  • Use normal PR/Issue Trackers