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