Your SlideShare is downloading. ×
Test driven documentation
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Test driven documentation

819

Published on

Given by Peter Neubuaer at OSON 2012: …

Given by Peter Neubuaer at OSON 2012:

You know the drill – prototype, code, test, docs. The last part of the chain is either omitted or will rot in Wikis and manuals. At Neo4j, we made the painful switch from wiki-hell to a totally code – backed manual that is driven by unit tests, a documentation toolchain and part of our build artifacts. Graph images, code snippets, live REST calls and everything. And still not getting in the way of the developers. We are now writing test code that is fit for publishing as blog links to parts of the manual. And developers are looking at the manual to see if the tests make sense. Want that? Hell yeah

Published in: Technology
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
819
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
2
Comments
0
Likes
3
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

×