Re: #29: Implement race condition tests

["atf trac notification" <nobody%julipedia.org@localhost>]

#29: Implement race condition tests
--------------------------+-------------------------------------------------
  Reporter:  jmmv         |       Owner:  jmmv
      Type:  enhancement  |      Status:  new 
  Priority:  minor        |   Milestone:  0.11
 Component:  MISC         |     Version:      
Resolution:               |    Keywords:      
--------------------------+-------------------------------------------------

Comment (by Garrett Cooper <gcooper@...>):

 I would think that stress/negative tests would be of more value than race
 condition tests (they're similar, but not exactly the same in my mind).

 In particular,

 1. Feed through as much data as possible to determine where reporting
 breaks down.
 2. Feed through data quickly and terminate ASAP. The data should be
 captured.
 3. Terminate child applications with unexpected exit codes and signals (in
 particular, SIGCHLD, SIGPIPE, exit codes that terminate, etc).
 4. Open up a file descriptor in the test application, don't close the file
 descriptor.
 5. fork(2) a process; don't wait(2) for the application to complete.

 There are other scenarios that could be exercised, but these are the ones
 I could think of off the topic of my head.

-- 
Ticket URL: <http://www.julipedia.org/projects/atf/trac/ticket/29#comment:3>
Automated Testing Framework <http://www.NetBSD.org/~jmmv/atf/>
Automated Testing Framework