This page (revision-44) was last changed on 17-Dec-2012 21:25 by Albrecht Striffler

This page was created on 17-Dec-2012 12:25 by Jochen Reutelshöfer

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
44 17-Dec-2012 21:25 5 KB Albrecht Striffler to previous
43 17-Dec-2012 21:22 5 KB Albrecht Striffler to previous | to last
42 17-Dec-2012 17:47 5 KB constin to previous | to last
41 17-Dec-2012 16:48 5 KB Jochen Reutelshöfer to previous | to last

Page References

Incoming links Outgoing links
How-To Create CITest
How-To Create CITest

Version management

Difference between version and

At line 4 changed one line
Knowledge engineering with KnowWE is supported by a continuous integration framework, that allows to embed automated tests on the knowledge. These tests are executed on regular bases (triggers can be configured) and in case of failure the users are alerted. An overview about the history and the testing results is provided on a dashboard. This allows for a safe development process. The use of the existing CI features is described [here|Doc CIDashboard]
Knowledge engineering with KnowWE is supported by a continuous integration framework, that allows to embed automated tests on the knowledge. These tests are executed on regular bases (triggers can be configured) and in case of failure the users are alerted. An overview about the history and the testing results in provided on a dashboard. This allows for a safe development process. The use of the existing CI features is described [here|Doc CIDashboard]
At line 48 changed one line
The actual test processing is executed within the method execute() of the Test-interface. As the first argument the test object is passed. The parameters, already being checked for consistency, are passed by as a String array. (In case of inconsistent parameters, the test is not executed at all, but a corrsponding error message is shown to the user or written to the logs.) Further, ignore parameters are passed, which allows the user to specify exceptional cases that should not cause the test to fail. This, however, makes sense only in very few cases an can be omitted otherwise.
The actual test processing is executed within the method execute() of the Test-interface. As the first argument the test object is passed. The parameters, already being checked for consistency, are passed by a String array. (In case of inconsistent parameters, the test is not executed at all, but a corrsponding error message is shown to the user or written to the logs.) Further, ignore parameters are passed, which allows the user to specify exceptional cases that should not cause the test to fail. This, however, makes sense only in very few cases an can be omitted otherwise.
At line 62 changed one line
%%prettify
At line 66 removed 2 lines
/%
At line 72 changed 16 lines
Once the test being implemented, it has to be registered on the plugin framework before it can be executed by the testing framework in a productive setting. Therefore, a particular extension point called ''CITEST'' exists. Hence, an entry within [plugin.xml|Meaning of plugin.xml] of the source modul has to be made.
The following listing contains an example entry for the test ''UnusedFlowTest''.
%%prettify
{{{
<extension plugin-id="d3web-Plugin-TestingFramework" point-id="Test"
id="UnusedFlowTest">
<parameter id="class"
value="de.d3web.tests.diaflux.UnusedFlowTest" />
<parameter id="name" value="UnusedFlow" />
<parameter id="description" value="CITest UnusedFlow" />
<parameter id="version" value="1.0" />
<parameter id="priority" value="5" />
</extension>
}}}
/%
Please be aware that the ''name'' parameter in this extension entry specifies the command name that needs to be used within the test configuration by the user. Therefore, be sure to use a meaningful and concise term there.
Once the test being implemented, it has to be registered on the plugin framework before it can be executed by the testing framework in a productive setting. Therefore, a particular extension point called ''CITEST'' exists.
At line 90 changed one line
howto create CITest
howto
This page (revision-44) was last changed on 17-Dec-2012 21:25 by Albrecht Striffler Top