🚀 [Feature] Add tests to detect and visualize changes in markdown converter

[darkdragon-001]

🚀 Feature

We should add tests for xml to markdown conversion. This way, every code changes producing a different conversion needs to modify the tests, too. This way, a reviewer can easily see the visual changes a certain pull request introduces.

[darkdragon-001]

We should create a list of features together with good example laws.

Suggestion:

• aappo: multi-level headlines, tables, quotes, appendix
• stvo: images

[ulfgebhardt]

What you can do is:

1. Copy 5 good examples of a law
2. Provide it as input for the 2markdown Converter
3. save the expected markdown output
4. On test compare those two

[darkdragon-001]

@ulfgebhardt That's the idea. I added my suggestions in #39 (comment). Any additional suggestions for those good examples of law?

[ulfgebhardt]

Nah I do not have a big knowledge on the data output of this repo. So having such a system in place with your examples is sufficient to have more examples going. Just remember to make it as generic as you can:
Have a folder with rawdata containing law1.rawdata - have a folder with md output data. Expect a file law1.md so its sufficient to just drop those two files in the corresponding folders.