PyModel/www/pmt.html at master · Python3pkg/PyModel · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
        "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<title>PyModel Tester</title>
</head>
<body>

<h2>PyModel Tester</h2>

<!--
<p>
<a href="http://staff.washington.edu/jon/">Jonathan Jacky</a>
-->

<p>
<a href="index.html">PyModel</a> is an open-source model-based testing
framework in Python.

<hr>

<p>
Usage:
</p>

<pre>
  pmt [options] models
</pre>

<p>
models is a list of one or more module names (with no .py suffix).
Each module named in models must contain
a <a href="concepts.html">model</a>, that is: a model program, an FSM,
or a test suite.  In addition, a module named in models can contain
additional configuration information for a model program.  Multiple
models (model programs including configuration, FSMs, and test suites)
are composed into a product.  The tester generates traces by executing
the product, at random or guided by the strategy option.  To just view
the traces, omit the implementation option.  To use pmt as an offline
test generator, omit the implementation option and use the output
option to save the traces in a test suite module.  To execute tests,
provide the implementation option.  To execute tests generated
offline, provide that test suite module as the single command
argument.  To generate and execute tests on-the-fly, provide one or
more model programs and/or scenario FSMs as command line arguments.
To save on-the-fly tests so they can be reproduced later, use the
output option to save them in a test suite module.
</p>

<p>
Limitations: pmt can only execute traces consisting of controllable
actions that the tester can call to make the implementation do
something.  Future versions will also support observable actions:
events that the tester can detect in the implementation.

<p>
Options:
</p>

<pre>
  -h, --help            show this help message and exit
  -a ACTION, --action=ACTION
                        Action to execute, as many as needed, if no -a execute
                        all actions
  -c CLEANUPSTEPS, --cleanupSteps=CLEANUPSTEPS
                        Maximum number of steps in the cleanup phase, default
                        0 for no cleanup
  -d, --debug           Run the main function in the debugger
  -e EXCLUDE, --exclude=EXCLUDE
                        Action to exclude from execution, as many as needed
  -g STRATEGY, --strategy=STRATEGY
                        Strategy (module name), omit to use random strategy
  -i IUT, --iut=IUT     Implementation (stepper module name), omit to just run
                        model
  -n NSTEPS, --nsteps=NSTEPS
                        Number of steps in a single test run before beginning
                        cleanup phase, default 0 for no limit
  -o OUTPUT, --output=OUTPUT
                        Output test suite module name (with no .py suffix), no
                        default (no output file if omitted)
  -q, --quiet           Omit arguments and return value from progress messages
                        (to suppress printing very large buffers etc.)
  -r NRUNS, --nruns=NRUNS
                        Number of test runs, default 1, 0 for no limit
  -s SEED, --seed=SEED  Random seed, use any nonzero value to make runs
                        reproducible
  -t SEC --timeout=SEC  Number of seconds to wait for stepper to return from
                        action before timing out and failing test,
                        default 0 (no timeout, wait forever).
                        (Might not work on Windows)
</pre>

<hr>

Revised April 2011

</body>
</html>