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 have following idea. When you write test cases as a documentation (see Kevlin Henney presentation https://www.youtube.com/watch?v=Qhz7cQQVBv4) you could be interested to generate some html page based on your integration tests describing technically how actually your test works. It would be nice to create asciidoc snippets per every test class. After all it could be used to compile full technical documentation. E.g. it could be useful for Spring Docs. Thanks to that you can keep your documentation always fresh. @JoseLion Let me know wdyt about it?
The text was updated successfully, but these errors were encountered:
@wyhasany, I think I see what you mean. I'm familiar with writing test cases as documentation. I think doing BDD is the best tool for that. Actually, that was one of the reasons for writing this plugin. 😁
If I understood correctly, you propose that the plugin could also generate asciidoc snippets based on the description of each test case. Is that correct? I think that would be a nice extra feature, and we can use the extension to enable it and add some customizations.
If you already have an idea of how to start implementing this, PRs are always welcome. We can start with something small and add more features to it progresively. 🙂
I have following idea. When you write test cases as a documentation (see Kevlin Henney presentation https://www.youtube.com/watch?v=Qhz7cQQVBv4) you could be interested to generate some html page based on your integration tests describing technically how actually your test works. It would be nice to create asciidoc snippets per every test class. After all it could be used to compile full technical documentation. E.g. it could be useful for Spring Docs. Thanks to that you can keep your documentation always fresh. @JoseLion Let me know wdyt about it?
The text was updated successfully, but these errors were encountered: