Requested by Emily Kund on DVS slack.
We would want a workflow that takes the input JSON file (similar to how we generate our markdown) and outputs a csv (or equivalent) file that folks could open with excel or google sheets. Ideally, we could even set up a central google sheet file to import this straight from a URL to this repo's github.io page and then stay up-to-date automatically.
Ideally the CSV is helpful for workbook activities, so there is a column added for tests performed, tests failed, notes from auditing, and perhaps also file names (for saving screenshots as images outside of the csv file).
Requested by Emily Kund on DVS slack.
We would want a workflow that takes the input JSON file (similar to how we generate our markdown) and outputs a csv (or equivalent) file that folks could open with excel or google sheets. Ideally, we could even set up a central google sheet file to import this straight from a URL to this repo's github.io page and then stay up-to-date automatically.
Ideally the CSV is helpful for workbook activities, so there is a column added for tests performed, tests failed, notes from auditing, and perhaps also file names (for saving screenshots as images outside of the csv file).