I've been putting off unit testing this code because I've been struggling to isolate the MkDocs plugin from the rest of the code.
I think the best compromise would be to move the logic out of the plugin class and keep only the configuration schema and the handlers for MkDocs plugin events there. We could then leave this code untested, but test the logic.
I've been putting off unit testing this code because I've been struggling to isolate the MkDocs plugin from the rest of the code.
I think the best compromise would be to move the logic out of the plugin class and keep only the configuration schema and the handlers for MkDocs plugin events there. We could then leave this code untested, but test the logic.