Please log in to watch this conference skillscast.
Quite a few books told you that writing tests upfront is a good thing. They're right, but unfortunately you normally also need some documentation about how to use the well tested service/applicaton.
Using "cucumber" makes both possible and "easy": Writing tests upfront, but also generating documentation from those tests. Accompanied with "aruba", you can use it to generate documentation from your tests for commandline applications. This is what cucumber and rspec do for their documentation.
This talk focuses on testing commandline applications and having documentation for those. It starts with thoughts about documentation itself and then gets into problems you might face if you try to convince administrators to document their scripts. It closes with a solution for that task.
YOU MAY ALSO LIKE:
- Jenny Martin and Pete Buckney's BDD From Start to Finish - Successful Delivery through Continuous Collaboration (in London on 26th - 28th February 2018)
- Gojko Adzic's Specification by Example: From User Stories to Acceptance Tests (in London on 27th - 28th June 2018)
- The Conference formerly known as Agile Testing & BDD eXchange 2018 (in London on 8th - 9th November 2018)
Living Documentation for commandline applications - A contract between you and your users
Dennis Günnewig is a system administrator responsible for a lot of HTTP proxy servers in large customer environments. To make his daily job a little bit easier he writes quite a few scripts and commandline applications. For those scripts and applications which are more complex he uses "cucumber" and "aruba" to write and run a test suite. Besides that he's one of the maintainers of "aruba" and loves to write ruby code.