# W3C Solid Community Group: Test Suite Panel

* Date: 2023-01-17T13:00:00Z
* Call: https://meet.jit.si/solid-test-suite
* Chat: https://gitter.im/solid/test-suite
* Repository: https://github.com/solid/test-suite-panel
* Status: Draft

## Present
* [Sarven Capadisli](https://csarven.ca/#i)
* [Michiel de Jong](https://michielbdejong.com)
* [Pete Edwards](https://id.inrupt.com/edwardsph)

---

## Announcements

### Meeting Recordings and Transcripts
* [W3C Solid Community Group Calendar](https://www.w3.org/groups/cg/solid/calendar).
* [W3C Solid Community Group Meeting Guidelines](https://github.com/solid/specification/blob/main/meetings/README.md).
* No audio or video recording, or automated transcripts without consent. Meetings are transcribed and made public. If consent is withheld by anyone, recording/retention must not occur.
* Join queue to talk.
* Topics can be proposed at the bottom of the agenda to be discussed as time allows. Make it known if a topic is urgent or cannot be postponed.

### Participation and Code of Conduct
* [Join the W3C Solid Community Group](https://www.w3.org/community/solid/join), [W3C Account Request](http://www.w3.org/accounts/request), [W3C Community Contributor License Agreement](https://www.w3.org/community/about/agreements/cla/)
* [Solid Code of Conduct](https://github.com/solid/process/blob/main/code-of-conduct.md), [Positive Work Environment at W3C: Code of Ethics and Professional Conduct](https://www.w3.org/Consortium/cepc/)
* Operating principle for effective participation is to allow access across disabilities, across country borders, and across time. Feedback on tooling and meeting timing is welcome.
* If this is your first time, welcome! please introduce yourself.

### Scribes
* SC
* MdJ
* PE

### Introductions
* name: text

---

## Topics

* SC: The Test Suite Panel is a horizontal team where test software developers, spec contributors, implementers, and any other group can join to discuss/collaborate.
* SC: This meeting is intended to focus on processing current open issues.

### Previous Meeting
URL: https://github.com/solid/test-suite-panel/blob/main/meetings/2022-12-15.md

### Next Meeting Plan
* SC: The recurring monthly event is in W3C Calendar and can be subscribed using: https://www.w3.org/events/meetings/0b451e91-287a-4987-8905-2ee92cd27355

### Overview
* SC: Wanted to talk about next steps and how we make the best of all work in the CG.
* SC: organize meetings by topics, treat them one by one in the meeting
* SC: remaining https://github.com/solid/test-suite-panel/issues issues 5,6,7, haven't had time yet to prepare PRs for these. let's try to resolve them asap, so we can point people to that.
* MdJ: we can use this hour for that

### Specify requirements and criteria for publishing test summaries and reports
URL: https://github.com/solid/test-suite-panel/issues/5
* ALL: Spent time reviewing https://github.com/solid/test-suite-panel/issues/5#issuecomment-1129987799
* MdJ: We discuss https://github.com/solid/test-suite-panel/issues/5#issuecomment-1129987799 point by point
* MdJ: We check https://solidservers.org/#footnotes to see if enough info is there about test assertions
* MdJ: In the context of https://github.com/solid/test-suite-panel/issues/7 we discuss https://solidservers.org/#context
* SC: maybe avoid having this in two places
* MdJ: yes, let's aim to move the statements from https://solidservers.org/#context into the policy and procedure documentation of the panel.
* PE: "This reports conforms to the procedures specified here: ..."
* PE: There, we might have different levels. The current reports are for instance not machine-readable. We are progressing towards a standard.
* PE: Equally the test harness doesn't allow implementers to provide any info for inclusion about why some tests are failing.
* SC: the test suite relates to these requirements in the same way that an implementation relates to the spec
* MdJ: Yes, it's good to say where there are some known issues
* We continue with item 4 of https://github.com/solid/test-suite-panel/issues/5#issuecomment-1129987799
* PE: we're not there yet
* SC: yes, I think item 4 is quite a journey. But if you can capture the status of a report, then maybe we're not stopped from linking to it.
* MdJ: A link from the spec has quite a bit of gravitas, so it makes sense to link from the spec to tests only after those tests have been approved by spec authors
* MdJ: we're done with https://github.com/solid/test-suite-panel/issues/5 then :)
* SC: this was productive

ACTION: SC to PR document about issue 5.