Commit 9e97208d authored by Alexander Diewald's avatar Alexander Diewald
Browse files

Testing-doc: GREEN

Issue-Ref: 3484
Issue-Url: https://af3-developer.fortiss.org/issues/3484

Signed-off-by: Alexander Diewald's avatarAlexander Diewald <diewald@fortiss.org>
parent 53601be9
documentation.html 4a3656e116229d2f1362e91a38f11da1bb672a63 YELLOW
documentation.html 7d19076ca7ce23ed67b0d29c2f59a5b225977a65 GREEN
......@@ -5,7 +5,8 @@
<title></title>
<meta name="generator" content="LibreOffice 6.0.5.2 (Windows)"/>
<meta name="created" content="00:00:00"/>
<meta name="changed" content="2018-08-22T17:10:07.622000000"/>
<meta name="changed" content="2018-08-23T17:37:44.106000000"/>
<meta name="created" content="00:00:00">
<meta name="created" content="00:00:00">
<meta name="created" content="00:00:00">
<style type="text/css">
......@@ -15,7 +16,6 @@
<body lang="en-US" dir="ltr">
<h1>Developer Documentation for the <i>AF3 Testing GUI
(org.fortiss.af3.testing.ui)</i></h1>
<h1><font size="5" style="font-size: 20pt">Plug-in description</font></h1>
<p>UI plug-in for org.fortiss.af3.testing. It hosts dedicated editors
which allow to edit the following objects:
</p>
......@@ -24,8 +24,8 @@ which allow to edit the following objects:
<p style="margin-bottom: 0cm"><tt class="western">TestSuite:</tt>
Its editor allows to modify inputs and expected outputs of each test
step. The editor also shows (with a pass/fail symbol) if the values
expected outputs and the simulated ones coincide (notice that the simulation might not be up to
date).
expected outputs and the simulated ones coincide (notice that the
simulation might not be up to date).
</p>
<li/>
<p><tt class="western">TestSuiteSpecification:</tt> Its editor
......
documentation.html cb149a150889b447726bfbb255511f556b1a51ac YELLOW
documentation.html 4be9f32363a7b12de00855d2c231ef6f78a8273b GREEN
......@@ -5,9 +5,11 @@
<title></title>
<meta name="generator" content="LibreOffice 6.0.5.2 (Windows)"/>
<meta name="created" content="00:00:00"/>
<meta name="changed" content="2018-08-22T17:24:46.890000000"/>
<meta name="changed" content="2018-08-23T17:36:15.039000000"/>
<meta name="created" content="00:00:00">
<meta name="created" content="00:00:00">
<style type="text/css">
p { margin-bottom: 0cm }
h2.cjk { font-family: "SimSun" }
h2.ctl { font-family: "Lucida Sans" }
tt.cjk { font-family: "NSimSun", monospace }
......@@ -23,52 +25,59 @@ generation and execution (simulation).</p>
<p>The plug-in contains, besides general classes like compositors,
constraints (to be removed when constraints are unified), model
implementation, etc, the following classes/packages:</p>
<p><br/>
</p>
<ul>
<li/>
<p style="margin-bottom: 0cm"><tt class="western">generator.modelchecking.GenerateTestSuiteCommand:</tt>
<p><tt class="western">generator.modelchecking.GenerateTestSuiteCommand:</tt>
It creates the <tt class="western">ITestSuiteGenerator</tt> and
calls the <tt class="western">generate()</tt> method for each type
of coverage that is active.</p>
<li/>
<p style="margin-bottom: 0cm"><tt class="western">generator.modelchecking.VerifyTestSuiteCommand:</tt>
<p><tt class="western">generator.modelchecking.VerifyTestSuiteCommand:</tt>
It checks that the expected and simulated outputs coincide.
Currently only used for checking refinement. Deprecated.</p>
<li/>
<p style="margin-bottom: 0cm"><tt class="western">method.random.generator:</tt>
It implements the <tt class="western">ITestSuiteGenerator</tt> for
<p><tt class="western">method.random.generator:</tt> It
implements the <tt class="western">ITestSuiteGenerator</tt> for
random criteria.</p>
<li/>
<p style="margin-bottom: 0cm"><tt class="western">pref:</tt>
Default values for parameters used in the test case generation, e.g.
number of steps, min/max values, NoVal probability, etc.</p>
<p><tt class="western">pref:</tt> Default values for
parameters used in the test case generation, e.g. number of steps,
min/max values, NoVal probability, etc.</p>
<li/>
<p style="margin-bottom: 0cm"><tt class="western">simulator.TestCaseSimulator:</tt>
It takes care of the simulation, creating <tt class="western">ExecutableComponent</tt>s
<p><tt class="western">simulator.TestCaseSimulator:</tt> It
takes care of the simulation, creating <tt class="western">ExecutableComponent</tt>s
and calling the corresponding <tt class="western">performStep()</tt>
method that does a complete single simulation step: A pre-step, the
step itself and a post-step. It can also set simulated/expected
outputs or compare both.
</p>
<li/>
<p style="margin-bottom: 0cm"><tt class="western">simulator.TestCaseExecutableComponent:</tt>
<p><tt class="western">simulator.TestCaseExecutableComponent:</tt>
It wraps one or more real <tt class="western">ExecutableComponent</tt>s,
which it contains as subExecutables. In every step the
<tt class="western">TestCaseExecutableComponent</tt> passes the
input values from the test case to the subExecutables.</p>
<li/>
<p style="margin-bottom: 0cm"><tt class="western">statistics:</tt>
It only contains Listeners. Most of the statistics related methods
are in the utils package. This package will be changed/removed once the testing plug-in is re-implemented. Deprecated</p>
<p><tt class="western">statistics:</tt> It only contains
Listeners. Most of the statistics related methods are in the utils
package. This package will be changed/removed once the testing
plug-in is re-implemented. Deprecated.</p>
<li/>
<p style="margin-bottom: 0cm"><tt class="western">validator.platform.*:</tt>
The idea of these packages was to execute the test cases in the
generated code (rather than in the design) using the abstractions
(interfaces) provided by the generic platform. Deprecated.</p>
<p><tt class="western">validator.platform.*:</tt> The idea of
these packages was to execute the test cases in the generated code
(rather than in the design) using the abstractions (interfaces)
provided by the generic platform. Deprecated.</p>
</ul>
<h2 class="western">Metamodel description
</h2>
<p>The testing metamodel describes test cases, coverage, statistics
and related constrains.</p>
<p><br/>
</p>
<ul>
<li/>
<p><tt class="western">TestSuiteSpecification</tt>: These
......@@ -80,8 +89,8 @@ and related constrains.</p>
<li/>
<p><tt class="western">TestSuiteSpecificationPart</tt>: Base
Class that will be extended to define different coverage criteria.
The active attribute is used to decide which kind of testing coverage shall
be fulfilled by the generation.</p>
The active attribute is used to decide which kind of testing
coverage shall be fulfilled by the generation.</p>
<li/>
<p><tt class="western">TestSuite</tt>: Each test suite
contains several <tt class="western">TestCase</tt>s. It is related
......@@ -106,13 +115,17 @@ and related constrains.</p>
given as a <tt class="western">ITerm</tt>. Each input belongs to a
unique <tt class="western">TestStep</tt>.</p>
<li/>
<p><tt class="western">TestOutput</tt>: Class representing
outputs of a <tt class="western">TestStep</tt>. Its expected value
is given as a <tt class="western">ITerm</tt>. Simulated values (also
<tt class="western">ITerm</tt>s) are kept to evaluate if the output
generated by the <tt class="western">Component</tt> matches the
expected output). Each output belongs to a unique <tt class="western">TestStep</tt>.</p>
<p style="line-height: 100%"><tt class="western">TestOutput</tt>:
Class representing outputs of a <tt class="western">TestStep</tt>.
Its expected value is given as a <tt class="western">ITerm</tt>.
Simulated values (also <tt class="western">ITerm</tt>s) are kept to
evaluate if the output generated by the <tt class="western">Component</tt>
matches the expected output). Each output belongs to a unique
<tt class="western">TestStep</tt>.</p>
</ul>
<p style="line-height: 100%"><br/>
</p>
<p>The sub-models <tt class="western">statistics</tt>, <tt class="western">coverage</tt>
and <tt class="western">constraintResults</tt> are deprecated. The
related features are planned to be re-implemented.
......@@ -120,6 +133,9 @@ related features are planned to be re-implemented.
<p>The random-specification-model metamodel describes a particular
case of a <tt class="western">TestSuiteSpecificationPart</tt>: Random
criteria.</p>
<p><br/>
</p>
<ul>
<li/>
<p><tt class="western">RandomSpecificationPart</tt>: It
......
random-specification-model.ecore b04f23eef5a265ffed25435e135c0ebd85ef2ac1 YELLOW
testing.ecore c2d12e3a1a99bb82278d6b4db6757f7e722de172 YELLOW
random-specification-model.ecore b04f23eef5a265ffed25435e135c0ebd85ef2ac1 GREEN
testing.ecore c2d12e3a1a99bb82278d6b4db6757f7e722de172 GREEN
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment