1This document defines the coverage for the fsync() function: 2 3Assertion Tested? 41 NO 52 NO 63 NO ** Synchronized I/O 74 YES 85 YES 96 NO 107 YES 118 NO: ** Not sure how to generate an I/O error 129 NO: ** Synchronized I/O 13 14NOTE: 15 16Assertion 1 is hard to test. Here cited the specification: 17 18It is reasonable to assert that the key aspects of fsync( ) are unreasonable to test in a test 19suite. 20That does not make the function any less valuable, just more difficult to test. A formal 21conformance test should probably force a system crash (power shutdown) during the test for 22this condition, but it needs to be done in such a way that automated testing does not require 23this to be done except when a formal record of the results is being made. It would also not be 24unreasonable to omit testing for fsync( ), allowing it to be treated as a 25quality-of-implementation issue. 26