FAQs and Troubleshooting

In this section:

How can I get quick access to information about usage on the command line?

Use the -help command line switch:

jtestcli.exe -help

How can I prevent my machine ID from floating?

Changes in the network environment may affect the interface that is used to compute your machine ID and result in machine ID instability. You can use the PARASOFT_SUPPORT_NET_INTERFACES environment variable to specify a stable interface and prevent the machine ID from floating.

1. Set up the PARASOFT_SUPPORT_NET_INTERFACES environment variable.

2. Set the variable value to a stable Ethernet network interface. Do not use virtual, temporary or loopback interfaces. 
   - On Windows: Set the value to the MAC address of your network card. You can use the ipconfig -all command to obtain the address.  For example:

   SET PARASOFT_SUPPORT_NET_INTERFACES=00-10-D9-27-AC-85

   - On Linux: Set the value to one of the network interfaces from the "inet" or "inet6" family. You can use the ifconfig command to obtain the list of available interfaces. For example: 

   export PARASOFT_SUPPORT_NET_INTERFACES=eth1

If the problem persists, you can obtain diagnostic information by setting up the environment variable PARASOFT_DEBUG_NET_INTERFACES and setting its value to true. This will print to the standard output the checking procedure that can be shared with technical support, as well as the interface that is used to compute your machine ID. The interface will be marked with the [SELECTED] prefix.

Why is coverage collected with the Jtest Plugin for Maven not associated with the executed tests on DTP?

DTP may fail to associate tests with their corresponding coverage if the coverage data was collected with the jtest:instrument goal. To ensure that tests and their coverage are properly associated, use the jtest:agent goal, or add the following flag to the command line when executing the jtest:instrument goal with Maven:

-Djtest.agent.newinstrumentator=false