You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it'd be easier to test the behavior of directives and if there were sample built pages to look out. As a model, matplotlib and sphinx gallery both build minimal documents to test their directives:
TL;DR is that tinybuild is designed as a minimal full sphinx doc build that you can run with make html from the tinybuild/doc to get a traditional build experience, but also gets run in test_full.py so you can check for html or rst output. So basically you can think of stuff in test_full.py as pytests that have access to a full site built with sphinx-build.
One gotcha at the moment is that you might need to run make clean in tinybuild/doc for the pytest version to run properly
generates all the output types, so you can easily test the html directly and that the other sphinx pages build
the ability to build the tinybuild docs independent of the tests makes it much easier to debug whether a test input is bad or the test is bad and why something is failing. Yes I can chase down the pytest cache directory but this is much easier.
I think it'd be easier to test the behavior of directives and if there were sample built pages to look out. As a model, matplotlib and sphinx gallery both build minimal documents to test their directives:
This isn't too different from the current sample output but I think more robust.
The text was updated successfully, but these errors were encountered: