Lax software development in Linux
Posted Sep 4, 2007 12:43 UTC (Tue) by jreiser
Parent article: LinuxConf.eu: Documentation and user-space API design
Michael presented three examples to show how the process of writing documentation can turn up bugs.
In each case there were no unit tests (by the orginal implementors or anyone else) and no coverage by Linux Test Project, yet the software was accepted. No one should be surprised at the shoddy results.
The software must stay in the -mm tree (or other staging area) until it is accompanied by a testcase which exercises each feature and error condition.
to post comments)