README.md

Testfest

To focus completely on testing and completing the Implementation Reports with a focus on Discovery and TD testing.

Note that the Profile spec will still be "mutable". While we might prototype some tests we will defer detailed testing of Profiles to another Testfest in mid-July (to be organized).

We also need to focus on gaps where features are at risk.

Logistics

• Date: 6-10 June 2022
• Time: (See doodle)
  • 8am Eastern/12pm UTC Monday and Tuesday
  • 7am Eastern/11am UTC Wednesday
  • 10am Eastern/2pm UTC Thursday, and Friday
• WebEx: see W3C Calendar
• Slack: Toumura resent invites; see email
• Hangouts: none
• VLAN: Toumura has confirmed is up; see email
• Other
  • Details to follow

Preparation

• Organize instructions in appropriate README.md files and index
• Update Implementation Report templates and provide links and instructions (McCool, Ege)

Contributions

If you are participating in the testfest, please do the following:

• Contribution to any specification

  • Provide an implementation description to https://github.com/w3c/wot-testing/tree/main/events/2022.06.Online/Architecture/Impls. You can find examples linked there. Make sure that the name of the implementation is the same across all possible contributions.
  • Provide a testimonial from your company at https://github.com/w3c/wot-testing/tree/main/events/2022.06.Online/Architecture/Testimonials. You can find examples linked there.

• Contribution to Discovery specification

  • (if you have a directory) Provide the TDs of your TDD to the TD specification at https://github.com/w3c/wot-testing/tree/main/events/2022.06.Online/TD . You need to group them under your implementation name, like intel-nodejs/TDs. These TDs will be used to generate the automatic results.
  • (if you have a directory) Fill in the TD manual.csv for the TD specification and submit it under the TD directory. This file is needed for the TD manual results, and is for the TD spec, not the WoT Discovery spec. This file should go in the folder of your implementation.
  • (if you have a directory) Automatically test your implementation with https://github.com/farshidtz/wot-discovery-testing and submit the automatic results at https://github.com/w3c/wot-testing/tree/main/events/2022.06.Online/Discovery.
  • For any discovery implementation, fill the Discovery manual.csv (https://github.com/w3c/wot-testing/blob/main/events/2022.06.Online/Discovery/manual.csv). Note that this is for the WoT Discovery spec, not the TD spec. It should be submitted like the automatic results above.

• Contribution to TD specification

  • Provide the TDs and TMs of your implementation to the TD specification at https://github.com/w3c/wot-testing/tree/main/events/2022.06.Online/TD . You need to group them under your implementation name, like intel-nodejs/TDs. These TDs will be used to generate the automatic results. You can see a contribution with both TD and TM at https://github.com/w3c/wot-testing/tree/main/events/2022.03.Online/TD/Ditto. NOTE: if your implementation is a pure consumer and does not have TDs, skip this step.
  • Fill in the manual.csv submit it. This file is needed for the manual results. This file should go in the folder of your implementation.
  • Optional: update batchValidation.sh
  • Example contribution: intel-nodejs

• Contribution to Profiles specification

  • Provide the TDs of your implementation to the TD specification at https://github.com/w3c/wot-testing/tree/main/events/2022.06.Online/TD . You need to group them under your implementation name, like intel-nodejs/TDs. These TDs will be used to generate the automatic results.
  • Fill in the manual.csv for the TD specification and submit it there. This file is needed for the manual results. This file should go in the folder of your implementation.
  • Provide the TDs of your implementation at https://github.com/w3c/wot-testing/tree/main/events/2022.06.Online/Profiles. Group it under your implementation, mimicking the file structure of the TD.

More detailed instructions can be found in the READMEs for each deliverable:

• TD
• Discovery

Please create an issue for any gaps that you are working on during the Testfest, and label them with Testfest 2022.06:

• Testfest 2022.06

Other Updates

After the input data has been updated as above, the following also needs to be done (by editors):

• Merge new inputs from event into data/input_2022
• Generate results
  • Discovery generates these directly
  • TD generates these using batchValidation script (run manually)
• Copy results over to appropriate delivery repo
  • testing/inputs/results
• Update Implementation Report Drafts
  • TD
  • Discovery