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

Setup automated testing across multiple Sphinx and docutils versions #59

Open
6 tasks
pradyunsg opened this issue Nov 7, 2023 · 0 comments
Open
6 tasks
Labels
type: task Something that needs to be done that is not a bug or feature

Comments

@pradyunsg
Copy link
Owner

pradyunsg commented Nov 7, 2023

The core idea here is, hopefully, obvious: This codebase needs to be tested to ensure that the output of builds using this theme is "correct".

The pieces that are needed for this would be:

  • The matrix-computation setup for determining the relevant Sphinx and docutils versions to test against.
  • The actual tests
    • Validating the output changes of the different knobs provided.
    • Validating the functional behaviours of each of the functional features provides.
    • Validating the bare-minimums of accessibility1.
    • Validating the visual presentation of specific elements.

Footnotes

  1. ... while being cognizant of measurability bias and that this alone doesn't mean that the answer for "is this accessible" is "yes" .

@pradyunsg pradyunsg added the type: task Something that needs to be done that is not a bug or feature label Nov 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: task Something that needs to be done that is not a bug or feature
Projects
None yet
Development

No branches or pull requests

1 participant