|
|
|
|
|
by thesuperbigfrog
706 days ago
|
|
>> How do you write automated tests for documentation? Somehow require that blocks of code have documentation linked to them? It could be tests to ensure documentation "builds" into all of the desired formats (e.g. web, pdf, ebooks, etc.) correctly. Some programming languages have the idea of "documentation tests". In Rust, tests that are part of the documentation will run as part of the documentation build: https://doc.rust-lang.org/rustdoc/write-documentation/docume... |
|
I admit that, while I write instructions for how to test specific functionality in gherkin, our company would not countenance publishing a non-narrative description of the system's behavior to our client's employees.
[0] https://www.manning.com/books/writing-great-specifications
[1] https://cucumber.io/docs/cucumber/step-definitions/?lang=jav...