Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reconsider format for commands.json and test files #75

Open
evmiguel opened this issue Feb 24, 2020 · 1 comment
Open

Reconsider format for commands.json and test files #75

evmiguel opened this issue Feb 24, 2020 · 1 comment
Labels
tests About assistive technology tests

Comments

@evmiguel
Copy link
Contributor

After reviewing #73, the following questions have come up:

  • Should commands.json that have been generated via script be committed?
  • What should the process be for generating test files? And should those files be committed?

If this repo will be moving to a pattern where files are generated, I envision a test runner or automation invoking the creation of such files.

@spectranaut spectranaut added the tests About assistive technology tests label Mar 11, 2020
@spectranaut spectranaut changed the title Solidify process on generating commands.json and test files Reconsider format for commands.json and test files Mar 11, 2020
@spectranaut
Copy link
Contributor

For me, the question here is: if these tests are declarative, we might want to get rid of the middle ground "test file" step and just have software that takes the CSV files and produces tests in an interface.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tests About assistive technology tests
Projects
None yet
Development

No branches or pull requests

2 participants