4.20.22 Meeting Minutes
Contents
4.20.22 Meeting Minutes#
Attendees#
Gabriel F.
Nick
Isabela
What are people working on?#
Please vote on jupyter/accessibility’s status in the new Jupyter governance by midnight wherever you are today!
Meeting this Friday, April 22: FAST-based JupyterLab UI toolkit. This is a discussion around the proposal for a new JupyterLab UI toolkit, which we’ve seen demo’ed for accessibility considerations. Show up or comment on the issue if you’d like to weigh in!
Isabela
Gabriel
A plan for the next six weeks that Quansight Labs is considering
A number of learnings about automated accessibility tests has been rolled into that doc
We are looking for pathways to contributions from other people - especially in this group
Nick
Model-based testing. Build a user model of somebody using the Jupyter test. A model is more interesting that a particular case because you get to weird error messages and corner cases that we need to test for.
A close example with stateful, property-based testing in Hypothesis
Workflow is not to do this all thinking about it as a test, but more as a state and task combo (ie. I’m looking at a notebook and I want to )
on the subject of building up a language to create test plans (Isabela metaphor: magnetic fridge poetry)
goal, action, goal, action, goal action (that’s a human-readable way we can work with)
https://github.com/robots-from-jupyter/robotframework-jupyterlibrary
https://github.com/ipython/traitlets/pull/705#issuecomment-1103958033
opt-in a11y checks - label on PR that goes into changelog