Aus ExpeccoWiki

Inhaltsverzeichnis 1 Language Settings 1.1 Supported Languages 1.2 Setting a default language 2 Printer Settings 2.1 Printer Type 2.2 Windows Printer Settings 2.3 Postscript Printer Settings 2.3.1 Print command 2.3.2 Page format 2.3.3 Margins 2.4 PDF Printer Settings 2.4.1 Page format 2.4.2 Margins 2.5 Color printing 2.6 Changing the default settings 2.7 Special note on postscript printing 3 Look & Feel Settings 3.1 General Settings 3.2 Code Editor Settings 3.3 State Colors 3.4 Sounds 4 Project Management Settings 4.1 Path Settings 4.2 expeccoNET Settings 5 Execution Settings 5.1 General Settings 5.2 Logging Settings 5.3 Debugging Settings 6 Report Settings 7 Company Settings 8 External Tools 9 PlugIn Settings 9.1 Available Plugins and Extensions

Language Settings

Supported Languages

The following languages are directly supported:

• German
• German (UML-Notation)
• English (UK)
• English (US)

Support for additional languages can be provided by eXept, third parties or yourself, by creating a corresponding language-translation file, which is to be placed into the "resources" directory of the expecco installation.

Setting a default language

When started, expecco sets the language from the shell environment variable "LANG" (Unix) or under Windows, from the users standard windows settings.

Therefore, to change the language, Unix/Linux users, may add a line such as:

setenv LANG de

or:

LANG=de
export LANG

to their login profile (if not already present).

Windows users should simply change their windows language setting.

Printer Settings

Printer Type

Choose the type of printer you have here. For Windows systems, please choose "Windows Printer" here. Unix (and Linux) users, should select "Postscript Printer". The "Postscript Printer" if selected will directly generate a postscript file which can be sent to a postscript printer. Likewise, a PDF document can be generated by selecting the "PDF Printer".

Depending upon installed expecco plug-ins and additions, you may find additional entries for other printer types here.

Windows Printer Settings

On the Windows operating system, a printer choice dialog will be shown when expecco is about to print for the first time, then remembers those settings as default value. This dialog allows for the selection of a printer among the list of available printers, the page format, the number of copies etc.

Via the "Setup" button, it also provides access to a printer-type-specific dialog to change the color, resolution and other printer-type-specific attributes.

Postscript Printer Settings

Print command

Specifies the command for printing. Typically, this is "lp" or "lpr". However, for previewing, or if you do not have a postscript printer available, you can also define it to save the output in some file:

cat > preview.ps

or filter it through ghostscript with:

cat > tmp.ps; ghostview tmp.ps

Processing the output with a postscript filter (like a2ps or enscript) is done by setting the printers type to dumb, and defining a command like:

a2ps | lpr

Page format

Page format setting is only possible (required) with a postscript printer or a PDF printer. Various standard formats are offered: the US formats letter, legal and ledger (which is landscape 17x11). The DIN formats include A4 through A6 and B5.

Margins

Margin setting is only possible (required) with a postscript printer or a PDF printer. You can set the margins either in inches or in millimeters.

PDF Printer Settings

Page format

Page format setting is only possible (required) with a postscript printer or a PDF printer. Various standard formats are offered: the US formats letter, legal and ledger (which is landscape 17x11). The DIN formats include A4 through A6 and B5.

Margins

Margin setting is only possible (required) with a postscript printer or a PDF printer. You can set the margins either in inches or in millimeters.

Color printing

Tells the system that the attached printer is a color printer. If turned off, documents are printed in black and white (b&w). Notice that most b&w postscript printers DO interpret color information, and use dithering techniques to simulate greyscales. Often, this does not produce the desired output, and better results may be obtained, by disabling this to force printing in black & white mode. (for example: the HTML documents' blue anchor texts looks ugly on a low resolution b&w printer).

Changing the default settings

The default settings and the list of offered print commands can be defined in a host-specific startup file. The original defaults are set in the "host.rc" startup file. To change these, create a file called "h_myHostName.rc" and add printer setup to this file (take the stuff found in "host.rc" as a starting point. To provide an example, our in-house setup is included (within a conditional based upon the systems domainName) in that file.

Special note on postscript printing

The ST/X postscriptPrinting classes currently do not know about correct font sizes on your printer (it will parse postscript font metrics files in later versions - if your system provides those metrics files). In order to find out a fonts size (especially height), ST/X asks the windowServer for the size of the corresponding screen font, and scales the returned value for the printer, using the displays resolution as a scaling factor. If your screen size in the display settings is wrong, that computation will lead to wrong results - be certain to give the correct dimension in the screen setting dialog. Wrong printer font sizes are also computed, if the displays font sizes are not correct (for example, when using 75dpi fonts on a 100dpi display).

Look & Feel Settings

General Settings

• Automatically Save Changed Items when Changing the Tree Selection
  If on, changes made on a tree element are automatically saved when selecting another tree element.
  If off, the user is asked whether to apply changes or not.
• Edit Name when Clicking in Selected Item
  If on, the name of a tree element can be edited by clicking on it.
• Automatic Edit Name of New Items
  If on, the name of a newly created tree element is automatically selected for editing it.
• Initially Select All when Editing Names
  If on, the whole name is initially selected when editing the name of a tree element.
• Select Tree Element on Right Click
  If on, a tree element is selected when right clicking on it.
• Keep Name of Copied Items when Pasting
  If on, the name of a tree element is kept when copy & pasting it.
  If off, a "Copy of ..." is added in front of the new element's name.
• Allow Duplicate Names
  If on, duplicate names for tree elements are allowed.
• Show an Item's Type-Icon in the Testplan Tree
  If on, an icon describing the type of a test-entry (Activity or Sub-Testplan) is show in testplans.
• Display the Testsuite's Filename in the Window Title Area
  If on, the filename of the testsuite is shown in the window title. Unless it has not been saved yet.
• Focus Follows Mouse
  If on, keyboard input is sent to the window under the mouse pointer (Unix behavior).
  If off, the user has to click on a window to associate the keyboard focus (Windows behavior).

Code Editor Settings

• Show Long Code Template Initially
  If on, a code template is added to a newly created elementary block which provides code examples.
• Show Pins in Code Editor
  If on, all input and output pins of the block are shown in the code editor too.
  This allows the user to copy the names of the pins into the source without switching between the schema and the code view.

State Colors

This dialog allows for the status colors (in lists and reports) to be choosen. By default, the colors are:

• Green for successful test runs / test items.

• Red for failed test runs / test items.
  A failure should be reported if the System-Under-Test (SUT) is incorrect.
  A failure-result requires action by the developer of the System-Under-Test.

• Dark Red for erroneous test runs / test items.
  An error is reported if the Test itself is malfunctioning. This means, that we do not know if the System-Under-Test (SUT) is correct.
  An error-result always requires action by the test-developer.

• Grey for inconclusive test runs / test items.
  The term inconclusive means, that for some reason, the test could not be executed (typically due to missing resources, measurement devices, databases etc.), and therefore, it is not known, if the System-Under-Test (SUT) is correct or not. Also, skipped tests are marked as inconclusive.
  An inconclusive-result requires action by the test-manager.

If you have red/green visibility problems, you may want to change the setting for better readability.

Sounds

Audio feedback via sound effects is sometimes useful, if your test is to be executed while you cannot watch the computers display. This may be because you have to operate the system under test, or handle measurement equipment, or because it is a long running test, and you want to be informed acoustically.

• Enable Sound Effects
  Use this checkbox to enable or disable all sound effects.
• TestSuite Started
  This sound is played when a testplan's execution is started. If this field is left empty, no sound is played.
• Pass
  This sound is played when a testplans's execution has finished. If this field is left empty, no sound is played.
• not PASSED
  This sound is played when a testplan's execution has finished with any non-passed testcase. If this field is left empty, the sound as specified in the previous field is played.

Project Management Settings

Path Settings

Currently only used by the file browser.

Allows the user to define a list of standard paths where test suites and libraries are located in. The browser provides fast access to this directories.

The default path of the file browser is set to the first entry into the list of standard paths. If the list is empty, the default path is set to the expecco's home directory.

expeccoNET Settings

expeccoNET is a separate product which performs requirements and defect tracking, test scheduling and automated execution. expeccoNET allows for automatic project tracking by using automated tests for requirement- and defect validation. expeccoNET is available from eXept Software AG. For more information, please consult our website.

Please ignore this document, if you do not have expeccoNET installed on a machine in your network.

The settings dialog allows you to configure the communication with an expeccoNET server. The expeccoNET server is responsible for the scheduling and automatic execution of test suites, storage of execution results and to keep track of the projects progress by associating test results with requirements and defects. In addition, it is also used as a central repository for test suites - both for sharing with other users and for revision control and versioning.

• expeccoNET Host
  Defines the host name of the machine where the expeccoNET server is being executed.
  If in doubt, ask the administrator, which is responsible for the expeccoNET installation and maintenance.

• expeccoNET Port
  Defines the HTTP port, which is used for the communication. Because the standard HTTP port (80) is both privileged AND often already in use by an apache server, an alternative portnumber such as 8080, 8081 is often used. If in doubt, ask the administrator, which is responsible for the expeccoNET installation and maintenance. (most often, the default 8081 is used).

• expeccoNET User
  Your username in the expeccoNET system. This is assigned by the expeccoNET administrator. It is typically NOT your username on the local machine and NOT necessarily the loginname on the expeccoNET host. If in doubt, ask the administrator, which is responsible for the expeccoNET installation and maintenance.

• expeccoNET Password
  Your password in the expeccoNET system. Again, this is initially assigned by the expeccoNET administrator and further maintained by yourself in expeccoNET. This is typically NOT the password on the local machine and NOT the password on the expeccoNET host.

• Remembering Common Setups
  To support the use of multiple servers and/or work under different user names, you can remember a given configuration and give it a unique name, for later retrieval via the "use configuration" comboBox.

Execution Settings

General Settings

• Separate Processes for Long-Running Activities (Initialized for Testsuite)
  This check toggle controls if multiple activities are allowed to execute in parallel (are executed by separate threads). By default, this is enabled, but for some programs, it makes sense to disable this feature. (Usually badly formulated activities, which do not care for synchronized access to shared data.)

• When execution longer than
  Due to the fact that starting up new processes is a slow operation and takes up some processing power, the expecco system delays the creation of new processes for some time, in order to allow for short activities to finish without the need for an expensive creation of a new process. If an activity is finished within that time duration, no new process is created. Effectively, short-term activities are sequentially executed, as long as their processing takes less than this time duration.

• Max. Number of Processes
  This limits the number of parallel executing separate processes. Because a process is a somewhat expensive resource in a computer (memory, disk space etc.), allowing for an arbitrary number of separate processes might lead to a slowdown or even blocking of the computers operation.

• Slow Motion Delay (Demo Mode)
  This parameter introduces a delay between the execution of individual activities. This is usually useful in demonstration or replay situations, where the user wants to visually follow and monitor the execution of the individual steps.

• Max. Number of Executors per Testsuite
  This limits the number of sub-executors that can be forked of a single testsuite. This parameter is used with special testplans, which run the same testsuite in parallel on multiple systems-under-test. This is only used in end-system acceptance tests, where multiple targets are to be tested in parallel.

• Max. Number of expeccoNET Test-Executions
  This limits the number of test suites that can be executed in parallel. This parameter is only used if the expecco application is also used as a slave processor for remote test execution, under the control of an expeccoNET server.

Logging Settings

• Log Activities
  If enabled, each activity is stored in an activity log.
  If disabled, only failed activities are stored.
  At least there is one activity log, which keeps the whole information about the execution.

• Log Pin Data
  If enabled, all input and output pin values are stored in the activity log. Otherwise all values are discarded.
  The default setting is specified in the testsuite.

• Log Info
  If enabled, all information messages are stored in the activity log. Otherwise all information messages are discarded.
  The default setting is specified in the testsuite.

• Max. Number of kept Subactivities per Activiy
  Maximum number of sub activities per activity stored in the activity log. This setting is used to limit the amount of logdata during execution. If nothing is specified, all sub activities are stored.
  The default setting is specified in the testsuite.

Debugging Settings

• Debug Activity Code
  Controls if a debugger is opened for errors/exceptions which happen while an activities' elementary code is being executed.

• Debug Pin Value Type
  Controls if a debugger is opened if the output value for a pin is not compatible with the pin's datatype. This is checked during execution.

• Debug 'halt' Messages
  Controls if a debugger is opened if a halt (aka "programmed breakpoint") is reached.

• Allow empty Activities (no Code or Steps)
  Controls if empty actions (i.e. unimplemented) are reported as an error.

• Debug all Exceptions
  Controls if a debugger should be opened for all exceptions; this includes internal notifications, such as inconclusive, success and failure notifications.
  By default, these internal notifications do not open a debugger.

• MessageTally on Execution
  Controls if the execution times of activities should be measured and an execution profile should be generated after the execution.

Report Settings

• Force this Report Settings
  Define the Report Template and Settings, used by the Report Generator for printing.
  If enabled, the report template and settings specified in the testsuite or testplan are used for printing.
  If disabled, the one and only Default Report Template is used.

• Output Format(s)
  Specify all output formats generated when using the Default Report Template.
  For each enabled output format a report is generated.

• Report Language
  Specify the language, used for the report when using the Default Report Template.

• Reset Initial State
  Resets the initial state of the Default Report Template.

• Output Directory
  Select the directory, where the outputs generated by the report generator are stored.

For editing the default report template see: Report Generation

Company Settings

The information entered here is used for the report generator only. If values are entered, corresponding placeholders from the report template are replaced with these.

• Company Name
  The name of your company.
• Principal Office
  The location of your principal office.
• Business Unit
  The name of your business unit.
• Responsible
  The responsible for this test.
• Login Name
  Use the login name as responsible. Can be combined with the host name.
• Host Name
  Use the host name as responsible. Can be combined with the login name.

External Tools

expecco may use external programs to provide additional functionality. This dialog allows for the configuration of which executable is used in particular.

Actually, the only tool to configure is the web browser. This is used to display html-formatted help texts.

PlugIn Settings

Expecco supports extensions called plugins. These can be loaded and unloaded dynamically using this plugin settings dialog. Plugins are provided by eXept or third party sources.
For more information, please refer to the documentation as provided with the plugin.

Available Plugins and Extensions

At the time of writing of this document, the following plugins and extensions are available or being developed by eXept.

• WEBTest Plugin
  The WEBTest plugin adds an interface to the Selenium Webtest framework. Selenium allows for capture/replay of web sessions and the validation of a web pages' contents.
  This plugin contains an import feature, which converts captured selenium sessions into an activity diagram. Also, a library consisting of web-page activities is included. Together, they allow for a recorded web session to be enhanced, refactored, reused or parametrized like any ordinary expecco activity diagram.
  
  Beside many other possible uses, two extra functionalities of this plugin add much to the value of the expecco product:
  • recorded web sessions can be augmented by semantic checks in the system under test. Especially the real effect of a web-transaction can be checked against the backend of a web application.
  • by feeding a recorded session's parameters through either a generator-block, or by reading a csv-file or a database, web-sessions can be parametrized. This can even be done dynamically on the fly, depending upon previus response data. For example, a set of boundary values can be read from a file and feeded as input parameter sets to a prerecorded websession, or the output of a webpage can be analyzed, transformed and used as input to another session or for a followup testcase.

• WSDL Import Extension
  

• XPDL Import Extension
  

• BPEL Import Extension
  

• XMI Import / Export Extension
  

The full online documentation can be found under: Online Documentation