Class Test Parameters - Dynamic Analysis

Dynamic Analysis

See description in Global Test Parameters.

Perform Dynamic Analysis

See description in Global Test Parameters.

Test Case Generation

See description in Global Test Parameters.

Automatic

See description in Global Test Parameters.

Test calling sequences up to length

See description in Global Test Parameters.

Test Methods

See description in Global Test Parameters.

public

Flag that controls if public methods are called directly.

protected

Flag that controls if protected methods are called directly.

package-private

Flag that controls if package-private methods are called directly.

private

Flag that controls if private methods are called directly.

Restricted Inputs

By default, Jtest will try to generate any input for the methods of the class. Use these nodes to restrict the inputs that Jtest will generate.

"THIS" object

Specifies what value Jtest will use by default when testing instance methods of the given class. Right-clicking this node displays a shortcut menu that allows you to set restricted inputs, add inputs from local repository, or add inputs from the global repository. This shortcut menu contains the following options:

Set Restricted Input: Lets you add a valid Java expression as a simple input value. If you reference classes that are not in the same package as the tested class, make sure to add import statements for these classes. For information about adding imports, see Specifying Imports.
Add From Local Repository: Contains menu items associated with the values available in the local repositories.
Choose an input's menu item to add that input to the node.
You can add inputs to the local repository in Class Test Parameters> Dynamic Analysis> Test Case Generation> Common> Inputs Repository.
Add From Global Repository: Contains menu items associated with the values available in the global repository.
Choose a menu item to add the input to the node.
You can add inputs to the global repository in Global Test Parameters> Dynamic Analysis> Test Case Generation> Common> Inputs Repository.

User Defined

Contains parameters that control the generation of the user defined test cases. [n]= number of test cases defined.

Method Inputs

Contains nodes that can be used to specify the set of inputs with which you want Jtest to test the class. [n]= number of test cases.

[Method name]

Use these nodes to specify the inputs to be used for the named method. [n]= number of test cases for this method.

[Argument name]

Use the associated shortcut menu to add valid Java expressions as input values to this argument. [n]= number of inputs for this argument.

Shortcut menu commands available include:

Add Input Value: Lets you add a simple input value.
Add From Local Repository: Contains menu items associated with the values available in the local repositories.

Choose an input's menu item to add that input to the node.
You can add inputs to the local repository in Class Test Parameters> Dynamic Analysis> Test Case Generation> Common> Inputs Repository.
Add From Global Repository: Contains menu items associated with the values available in the global repository.

Choose an input menu item to add the input to the node.
You can add inputs to the global repository in Global Test Parameters> Dynamic Analysis> Test Case Generation> Common> Inputs Repository.
Delete All Inputs: Removes all existing inputs.

Test Classes

Test classes let you add test cases that are too complex or difficult to be added as method inputs. A test class is a class that extends jtest.TestClass and is used to specify test cases that Jtest should use to test the class. You can write your own test class, or use your JUnit classes. For information on adding Test Classes, see Adding Test Classes.

[n]= Total number of test cases defined by all of the test classes.

Common

Contains parameters shared by both automatic and user-defined test case generation.

Imports

Contains imports shared by all the code used in the specification. See Specifying Imports for more information.

Static Class Initialization

See description in Global Test Parameters.

Inputs Repository

See description in Global Test Parameters

Test Case Execution

See description in Global Test Parameters.

Execute Automatic

See description in Global Test Parameters.

Execute User Defined

See description in Global Test Parameters.

Stubs

See description in Global Test Parameters.

Options for Automatic Test Cases

See description in Global Test Parameters.

Use Automatic Stubs (white-box stubs)

See description in Global Test Parameters.

Use User Defined Stubs

See description in Global Test Parameters.

Options for User Defined Test Cases

See description in Global Test Parameters.

Use User Defined Stubs

See description in Global Test Parameters.

"Tested Set" Includes

See description in Global Test Parameters.

Stubs Class

Indicates what stub class to use while testing this class. If you use the token $DEFAULT, Jtest will automatically search for and use a class named (class_under_test_name)Stubs that extends jtest.Stubs. To enter the specific location of the appropriate stubs class, right-click this option, choose Edit from the shortcut menu, then enter the path to the stubs class.

For more information on stubs, see Testing Classes That Reference External Resources and Using Custom Stubs.

Pre-filtering Suppression Categories

See description in Global Test Parameters.

Exceptions in Throws Clause

See description in Global Test Parameters.

DirectIllegalArgumentExceptions

See description in Global Test Parameters.

Explicitly Thrown Exceptions

See description in Global Test Parameters.

Exceptions Caught By Empty Catch

See description in Global Test Parameters.

DirectNullPointerExceptions

See description in Global Test Parameters.

Automatically Instrument "Design by Contract" Comments

See description in Global Test Parameters.

Test Case Evaluation

Contains parameters that control test case evaluation. For more information about test case evaluation, see Viewing and Validating Test Cases.

Report Uncaught Runtime Exceptions

See description in Global Test Parameters.

Perform Automatic Regression Testing

See description in Global Test Parameters.

Specification and Regression Test Cases

These test cases are used as reference test cases when Jtest performs regression and black-box testing. When tests are run, the outcomes for the run are compared with these outcomes. If a discrepancy exists, an error is reported.

Jtest automatically adds the automatic test cases that increase coverage to this list. All user-defined test cases are added.

Shortcut menus let you specify whether outcomes are correct or incorrect.

If you change specification and regression test cases and want to restore the set used during the actual tests, right-click the Specification and Regression Test Cases node, then choose the Reload option from the shortcut menu. Jtest will then reload the original test cases.

[method name]

Contains test cases for this method.

Test Cases

Contains all the information for a test case.

Test Case Input

Input that defines the test case.

The input for automatic test cases is the calling sequence.

Outcomes

Outcomes for this test case. Verify if the outcomes are correct or incorrect according to the class specification and set their state using the shortcut menus.

When the outcome is an object, Jtest automatically chooses the toString method to show its state.

If a method named jtestInspector is defined for the object's class, Jtest will only use the return value of this method to show the object state.

If no toString or jtestInspector methods are defined, Jtest will heuristically choose some public instance methods for that object to show its state.

If the method under test is a static method, Jtest will heuristically choose public static methods to show the class state. If the methods Jtest chose are not enough, declare a static method called sjtestInspector for the class. Jtest will use the return value of this method to show the object class.

[n]= number of outcomes for this test case.

Exceptions

Indicates whether an exception occurred, and, if so, what type of exception occurred.