This page (revision-26) was last changed on 23-Jun-2015 15:04 by Albrecht Striffler

This page was created on 17-Dec-2012 16:38 by Joba Baumeister

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
26 23-Jun-2015 15:04 3 KB Albrecht Striffler to previous
25 17-Dec-2012 17:24 3 KB Joba Baumeister to previous | to last
24 17-Dec-2012 17:04 2 KB Joba Baumeister to previous | to last
23 17-Dec-2012 17:03 2 KB Joba Baumeister to previous | to last
22 17-Dec-2012 17:02 2 KB Joba Baumeister to previous | to last
21 17-Dec-2012 17:01 2 KB Joba Baumeister to previous | to last

Page References

Incoming links Outgoing links
Tutorial Printer Testcases
Tutorial Printer Testcases

Version management

Difference between version and

At line 1 added 7 lines
!!! Defining Automated Test Cases
It is possible to define test cases for a knowledge base within the wiki.
For each test case the answers of questions together with the expected solutions are described.
In the examples below, one test case for an "unpowered printer" and one test case for an "unconnected printer" is depicted.
{{{
At line 14 added 3 lines
%
%%TestCase
At line 23 added one line
}
At line 25 added one line
}}}
At line 27 added 26 lines
When inserting the test cases into an article, they are printed as below:
%%TestCase
No power on printer {
Please specify your problem = Printer does not print,
Please check the power supply of the printer = Printer is not connected or power is off :
No power supply (established);
}
%
%%TestCase
Unconnected printer {
Please specify your problem = Printer does not print,
Please check the power supply of the printer = Printer is connected and power is on,
How is the printer connected to your computer = Connected by cable,
Is the cable plugged into the printer and the computer = No :
Cable not connected (established);
}
%
!!! Running Test Cases
A test case player can be inserted into an article by using the following markup
{{{
At line 56 added one line
}}}
At line 58 added 3 lines
Please note, that in the {{uses}} annotation the package name of your knowledge base project needs for be defined.
When saving the article, the following interface is shown.
Here users can play the test cases automatically and see whether the expected solutions are derived by the current version of the knowledge base.
At line 62 added 44 lines
%%TestCasePlayer
%
!!! Continuous Integration of Knowledge Bases
The execution of test test cases can be automated by creating a continuous integration dashboard.
Here, some static verification methods can be applied as well as the test cases.
The following markup introduces a continuous integration dashboard:
{{{
%%CIDashboard
@trigger: onSave "Tutorial Printer Problems"
@name: Continuous Integration of Printer Problems Knowledge Base
@test ArticleHasErrors "Tutorial Printer Problems"
@test TestCase "Tutorial Printer Testcases/No power on printer" "Tutorial Printer Problems"
@test TestCase "Tutorial Printer Testcases/Unconnected printer" "Tutorial Printer Problems"
@test CombinedFlowRuleAbstraction "Tutorial Printer Problems"
@test CombinedFlowRuleSolution "Tutorial Printer Problems"
@test NoAutostart "Tutorial Printer Problems"
@test UnusedNode "Tutorial Printer Problems"
@test UnusedFlow "Tutorial Printer Problems"
%
}}}
When saving the article, the following dashboard appears:
%%CIDashboard
@trigger: onSave "Tutorial Printer Problems"
@name: Continuous Integration of Printer Problems Knowledge Base
@test ArticleHasErrors "Tutorial Printer Problems"
@test TestCase "Tutorial Printer Testcases/No power on printer" "Tutorial Printer Problems"
@test TestCase "Tutorial Printer Testcases/Unconnected printer" "Tutorial Printer Problems"
@test CombinedFlowRuleAbstraction "Tutorial Printer Problems"
@test CombinedFlowRuleSolution "Tutorial Printer Problems"
@test NoAutostart "Tutorial Printer Problems"
@test UnusedNode "Tutorial Printer Problems"
@test UnusedFlow "Tutorial Printer Problems"
%
This page (revision-26) was last changed on 23-Jun-2015 15:04 by Albrecht Striffler Top