UseCases.unittest_subprocess.binaries.noopts.EXITOK package

Submodules

UseCases.unittest_subprocess.binaries.noopts.EXITOK.CallCase module

example_D

Case for a testee with success, exit 0: EXITOK

EXIT:
0
STDOUT:
arbitrary output arbitrary signalling OK string arbitrary output
STDERR:
class UseCases.unittest_subprocess.binaries.noopts.EXITOK.CallCase.CallUnits(*args, **kargs)[source]

Bases: epyunit.unittest.subprocess.TestExecutable

setUp()[source]
classmethod setUpClass()[source]
testCase000()[source]
testCase010()[source]
testCase011()[source]

Module contents

The UseCase EXITOK demonstrates and verifies the basic facilities start of a script by epyunit.SysCall.

  • CallUseCase.py

    The main primary call of the UseCase. In dialogue mode this should be started by PyDev debugger from Eclipse.

  • epyunit/myscript.py

    The script provides hard-coded response output for the test of ePyUnit itself, but also wrapper processes in general.

The following figure depicts the components.
+------------------+         +-------------+
|                  |         |             |
|  CallUseCase.py  |  <--->  | myscript.py |  
|                  |         |             |
+------------------+         +-------------+
         A                          A
         |                          |
      UseCase                   a resource
   frame for tests               simulator