This page (revision-32) was last changed on 24-Feb-2016 11:05 by Albrecht Striffler

This page was created on 20-Nov-2012 14:36 by UnknownAuthor

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
32 24-Feb-2016 11:05 4 KB Albrecht Striffler to previous
31 17-Dec-2012 15:44 4 KB Albrecht Striffler to previous | to last
30 17-Dec-2012 15:05 4 KB Jochen Reutelshöfer to previous | to last
29 17-Dec-2012 15:05 4 KB Jochen Reutelshöfer to previous | to last
28 17-Dec-2012 15:05 4 KB Jochen Reutelshöfer to previous | to last
27 17-Dec-2012 15:05 4 KB Jochen Reutelshöfer to previous | to last
26 17-Dec-2012 14:59 4 KB Jochen Reutelshöfer to previous | to last
25 17-Dec-2012 14:59 4 KB Jochen Reutelshöfer to previous | to last
24 17-Dec-2012 14:59 4 KB Jochen Reutelshöfer to previous | to last
23 17-Dec-2012 14:57 4 KB Jochen Reutelshöfer to previous | to last
22 17-Dec-2012 14:51 4 KB Jochen Reutelshöfer to previous | to last
21 17-Dec-2012 14:50 4 KB Jochen Reutelshöfer to previous | to last

Page References

Incoming links Outgoing links
Testing-App
Testing-App

Version management

Difference between version and

At line 1 removed 3 lines
[{TableOfContents}]
At line 10 removed one line
At line 13 removed one line
At line 22 removed 4 lines
The installation requires the following components to be installed:
* Oracle Java 8 or newer (http://www.java.com)
At line 28 changed 2 lines
The application comes in two installation variants: An executable java version and a MS-Windows executable. For both variants the required libraries (lib) are included.
The application is started by double-clicking the executable (jar or exe). Alternatively, you can use the command line version for more options:
%%todo
Write Testing-App description.
At line 31 changed 36 lines
{{{> java –jar TestingApp.jar [OPTIONS]}}}
The available options are as follows (the default values are given in parentheses):\\
__-k__ name of the knowledge base file to be tested (knowledgebase.d3web)\\
__-t__ name of the test configuration file (TestConfig.txt)\\
__-o__ name of the test report output file (build_<timestamp>.xml)\\
__-help__ showing a help description of these parameters\\
__-?__ showing a help description of these parameters\\
!! Configuration
The testing tasks that are executed by the application are defined in the test configuration file. The name of the file name can be passed to the application with the command line call using the parameter ‘t’. If the parameter is omitted a file with the name TestConfig.txt will be used by default.
The textual format of the file is described as follows:
* Each line in the file defines one testing task. Comments can be inserted (or tasks deactivated) using the comment signs ‘//’ at the beginning of the line.
* In a line a task is defined by a space separated item list. Expressions containing spaces need to be enclosed in double quotes (e.g., “my knowledge base”).
** The first item is the name of the test to be executed. This item is non-optional.
** The second item is an identifier for the test objects (one or multiple), which the test will be applied on (e.g., name of a knowledge base). To identify multiple test objects regular expressions can be used (e.g., “.*”). This item is non-optional.
** Additionally, configuration parameters for the test can be specified. Any items defined after the test object identifier will be passed to the test as configuration parameters. The amount and nature of possible configuration parameters depends on the respective test at hand. A description of the required and optional parameters of all tests can be found within the description of the respective test in Chapter 4 of this manual.
The format of this configuration file is to some extent similar to the way tests are specified in the continuous integration dashboard in KnowWE. A line in the dashboard markup beginning with @test: specifies a testing task in a similar way as employed in the testing application. That is, a test line of a KnowWE dashboard markup can be transferred to a task definition in the testing application configuration file by using copy&paste.
\\
\\
Example:
[{Image src='test-syntax.png' width='400' height='..' align='left|center|right' style='..' class='..' }]
!! Tests
The Testing-App comes with a number of tests for d3web knowledge bases. An enumeration and descriptions of the tests and their option parameters can be found [here|Doc CIDashboard]. (Note: The tests working on 'Article' as test object class are not available in the stand alone version of the Testing-App.)
!!Licence
This application
@user: Jochen Reutelshöfer
%
This page (revision-32) was last changed on 24-Feb-2016 11:05 by Albrecht Striffler Top