A possible (test-driven-development-like) Web2Cit workflow is:
- Find a target URL that returns unexpected results in Citoid
- Confirm Web2Cit returns unexpected results as well
- Write a test for the target URL
- Write a template for the target URL until all domain tests pass. Write patterns if needed.
- Repeat
To support this workflow, we need a way to check how test results change after making configuration changes. This will be supported by the Web2Cit-Editor.
In the meantime, consider providing an additional endpoint (maybe just the debug endpoint T301748 with a search query ?tests) that shows these results.