Re:Ultratestable Coding Style
by calpaterson on Tuesday June 09, 2015 @07:19AM
(#9685155)
For a filesystem integration, perhaps you can generally rely on the documentation being correct. There are lots of integrations (main cause of side effects) where this is not the case, for example if you are integrating with APIs or with a SQL database. For these cases I would want to have more than an umbrella test to check that my assumptions about the integration are correct.
[ Parent
| on HN ]
Race conditions in file systems are fun. So are edge conditions around partially written data (for instance, Windows NT will transactionally guarantee a file's existence, but not its content).
Re:Ultratestable Coding Style
by developer1 on Wednesday June 10, 2015 @01:32AM
(#9690251)
Testing the filesystem? This talk is interesting as hell, outlines how FoundationDB goes about testing unusual failures in systems like the filesystem and the network stack: https://www.youtube.com/watch?v=4fFDFbi3toc . Crazy beyond all belief.