• Overview
• CTE
• Model-based Testing
• Specification-based Testing
• Tessy
• Time Partition Testing

Functional Testing: CTE Tips

Overview

• Creating new test cases
• Logical dependencies and test case generation
• Specification of logical dependencies
• Specification of combination rules
• Drag & Drop elements into dependency and test case generation editor
• Dependency Manager
• Adding Tags
• Adding new Icons
• Alternative View
• Error message while installing CTE XL
• Requirements are not imported from Doors
• Error while installing CTE XL: "Magic number did not match"
• "Sorry, your license key is not valid" message
• "Can't connect to specified Server please check your URL" message
• Command Execution Error message while starting CTE XL
• This application has failed to start because MSVCR71.dll was not found.
• Error using the DOORS requirements import caused by Kaspersky Internet Security.

Creating new test cases
To create new testcases the insert key (Ins or Einfg) can be used while the input focus lies on the testcase tree or on the combination table.
Top

Logical dependencies and test case generation
The CTE XL distinguishes

• logical dependency rules to specify dependencies between the classes of the classification tree (Tools->Dependencies), and
• combination rules for the generation of test cases (Tools->Generate Test cases).

Top

Specification of logical dependencies
Dependency rules are specified using propositional logic. All logical operators allowed can be selected via the corresponding buttons of the dependency editor (Tools->Dependencies).
Top

Specification of combination rules
To specify the combination rules for the test case generation the CTE XL offers five different mechanisms (Tools->Generate Test cases). Logical dependencies specified will be taken into account when generating test cases automatically.

• Using the name of a class in a combination rule indicates that this class should be selected in at least one test case. In the case that the class is further divided into subclasses the use of the class in a combination rule indicates that at least all possible combinations of the subclasses should be generated.
• Using the name of a classification in a combination rule indicates that all classes of the classification should be selected in at least one test case. In the case that the classes of the classification are further divided into subclasses the use of the classification in a combination rule indicates that all possible combinations of the subclasses should be generated at least once.
• A * B: all patterns to be generated for A should be combined with all patterns to be generated for B. Example: for two classifications X and Y with classes x1, x2 and y1, y2, (X * Y) results in the generation of the for test cases (xi, yj). It is also possible to specify a combination rule (x1 * Y) which results in a combination of x1 with all the classes of the classification Y.
• A + B: all patterns to be generated for A and all patterns to be generated for B will be produced and combined in test cases in an unsystematic way. This operator guarantees the generation of all specified patterns and tries to minimize the number of test cases generated.
• twowise(A1, A2, ...); threewise(A1, A2, ...): generates a pair-wise or three-wise combination of all the patterns specified by Ai. Example: for three classifications X, Y, Z with classes xi, yi, and zi twowise(X, Y, Z) will generate all pairs of classes for X and Y (xi, yi), for X and Z (xi, zi), and for Y and Z (yi, zi). The operator tries to minimize the number of test cases generated.

Top

Drag & Drop elements into dependency and test case generation editor
For the specification of dependencies and combination rules, it is possible to drag & drop elements of the classification tree into the dependency editor and the test case generation editor.
Top

Dependency Manager
The correctness of test cases with respect to the logical dependencies specified is only checked when the dependency manager is activated. The dependency manager can be activated by pressing down the lamp symbol from the short cut buttons. Red colored test cases indicate a violation of dependencies, green colored test cases indicate correct test cases. Yellow colored test cases indicate test cases not checked with respect to the logical dependencies. This will only occur if the dependency manager is turned off.
Top

Adding Tags
You can add an existing tag to any tree node or testcase using the "Tags" dialog (Tools->Tags...). On the left you will see all tags that are currently installed in the CTE. Select one of these tags to see and edit the tag's properties. Once installed, the name and type cannot be changed anymore, but you can specify an icon and the icon's position in the tree node. The "traffic lights" are used to specify where the tag can or must be added and where it is not allowed. Using this dialog you can also create new tags by pressing the "Create" button. Chose one of the tag types and give it a name. Specify the icon and position and click on "Apply" to add the new tag to the list on the left. Finally close the dialog, right-click a test case or tree node and select "Available Tags". Here you can add any allowed tags to the test case or tree node.
Top

Adding new Icons
Besides the list of integrated icons you can add your own icons to the CTE. To do so, go to the general preferences dialog and chose the "Icons" tab. Right-click on the list of icons (this list is empty, after you have installed the CTE). Chose "New" in the shown popup menu. A dialog appears where have to specify a name for the icon. This name will be used later on to identify the icon. (Note that if you specify a name which is already in use, the existing icon will be replaced !) Now the icon is displayed in red color (because no image file has been specified yet) in the icon-list. Select the icon and specify a filename of a GIF or JPG picture, that you want to use as the new icon.
Top

Alternative View
An alternative view can be chosen from the pop-up menu in the test case table for coloumns representing a folded classification. In alternative view the selected class names will be shown instead of the marks.
Top

Error message while installing CTE XL: Win32 Error:234 File:"Win32Util.cpp" Line:1425
If you have a Windows login name which contains non-ASCII characters, such as ä, é, chinese or japanese characters, the installer can not access the directory of your TMP environment variable. There are 2 possible ways to solve this problem:

1. If you have administrator rights and are using a local user account, you can change your login name. In Windows XP, proceed to Start, Control Panel, User Accounts. Select your login name, click on Properties, change your login name to a name that only contains common ASCII characters (such as A,...Z, a,...z) and click on Apply. Log off and log on again using the new login name.
2. Proceed to Start, Control Panel, System, Advanced, Environment Variables. In the upper variable field, search for the variable TMP and select it. Click on Edit, erase the contents and enter a pathname e.g. C:\Temp. Click on OK, log off and log on again.

Try to run the setup program again.
Top

Requirements are not imported from Doors
CTE XL can import only requirements which do not contain headings. To make sure the requirements you whish to import do not contain headings, right-click the requirement in Doors, click on Properties, then click on the General tab. The upmost text field should be empty.
Top

Error while installing CTE XL: "Magic number did not match"
The installer file you downloaded is most likely corrupted or incomplete. Please try downloading the installer again from our website. If the problem still remains, please contact our support: cte@systematic-testing.com.
Top

"Sorry, your license key is not valid" message when entering the license key for registration
Make sure you downloaded and installed the newest version of CTE XL from this website. Then, complete the following steps:
1. If CTE XL is running, close the application.
2. Delete the file "cte_config.cfg" which is located in your user home directory, usually "C:\Documents and Settings\<username>".
3. Restart CTE XL and repeat the registration process.
If the problem persists, please contact the CTE XL support: cte@systematic-testing.com.
Top

Error message while trying to connect to Testdirector: "Can't connect to specified Server please check your URL. TestDirector error Code: 16387."
1. The coupling only works if the TestDirector client is installed on your workstation. To install the TestDirector client, open an internet browser (IE, Firefox...) and visit the start page of the TestDirector server. The link should look something like: http://host_xyz.testdirector_server.com/tdbin/start_a.html. After you have entered the link an ActiveX-Script starts to install the TestDirector client (please consider that you need admin rights to install the client). You can find the installed client in C:\Program Files\Mercury Interactive\TD2000_80.
2. The URL for the CTE XL-TestDirector-Wizard should look something like: http://host_xyz.testdirector_server.com/tdbin/ (please consider that there is no html-file in the URL!!!)
3. Please ensure that you have correct proxy settings for your current connection. If you are not sure, please contact your network administrator to clear this point.
Top

Command Execution Error message while starting CTE XL: "Failed to create server socket: Permission denied: listen failed"
This error occurs if your AntiVirus/-Spyware or Firewall tool has blocked cte.exe. CTE XL is not a spyware or malware. CTE XL is checking via TCP/IP if a another instance of CTE XL started on your computer, this action causes the spyware/firewall warning.
To avoid this error please allow cte.exe TCP/IP traffic.
Top

This application has failed to start because MSVCR71.dll was not found. Re-installing the application may fix this problem.
This error occurs if the MSVCR71.dll is not located in the MS Windows system folder. To fix this problem, copy this file to the folder the cte.exe is installed in. In case the MSVCR71.dll can be found under "(cte install folder)\jre\bin".
Top

Error using the DOORS requirements import caused by Kaspersky Internet Security.
Under rare circumstances Kaspersky Internet Security deletes the CTE.exe when initializing a connection to DOORS. Putting the CTE.exe on Kaspersky's white list solves this problem.
Top