Kevin Ali admin


Kevin Ali
Last Active
Admin, Staff
  • Re: cppTest 10.x with VS2015 plugin

    Yes, cpptest 10.x does support vs2015.

  • Re: Static report

    What version of C++ test are you using

    Where you able to run static analysis on our example project?
    Did you generate a BDF for this project?

  • Removing DTP engine results from DTP

    Please note this will only work with DTP Engines.

    To delete data that has been published to DTP from a DTP Engine, you will need to you will need to use the "Build Administration - Statistics" Widget.

    The result/reports from DTP Engine when published to DTP will be given a Build ID. The Build ID will uniquely identify the project. Each test that is ran will be normalized into that specific build. It is not possible to remove a specific test configuration run.
    Within DTP Please add the "Build Administration - Statistics" Widget. You can navigate to this widget by the below screen shot.

    Once the widget has been created the widget should look like the following.

    If you click the widget itself you will navigate to the following page you will notice that this will list all the builds, that have been publish. By clicking the trash can icon you will delete the build. Deleting the build will remove the data permanently. Please be aware of what you are deleting, once the data has been deleted there is no recovery tool or undo.

  • How to un-lock a workspace after a force-close

    Parasoft-Test based products (such as SOAtest, Jtest, or Virtualize) are shipped as Eclipse plugins. When Eclipse starts, it opens a workspace - locking it so that other Eclipse instances cannot use the same workspace at the same time. When Eclipse shuts down, this workspace is then un-locked.

    When one of these products becomes unresponsive and must be force-closed (or killed in Linux), or the machine unexpectedly restarts, the workspace may not be un-locked on shutdown. When this happens, you will see an error when re-starting the application: "The specified workspace is in use".

    Follow these steps:
    Go to the workspace and open a folder called .metadata (note: on Linux, this is a hidden folder).
    Find and delete a file called .lock
    Try starting the application again - it should now open the workspace without issues.

  • Could not create the Java Virtual Machine

    If you receive a start-up error when starting a Parasoft Test tool with the error message:

    "Error: Could not create the Java Virtual Machine. Error: A fatal exception has occured. Program will exit."

    followed by another message popup (see images in solution), this may mean there is not enough continuous memory to allocate for the JVM. The solution is to decrease the maximum heap space allocated for the JVM.

    By default, the JVM the Parasoft tools use requests 1024m/2048m of continuous memory for the heap space. This error is usually occurs because there is not enough continuous memory on the machine, therefore the JVM cannot be created. In this situation, the solution is to decrease the requested JVM heap size.

    1) Open up the eclipse.ini file in the Parasoft Test installation directory. (ex. C:\Program Files\Parasoft\Test\9.5\eclipse.ini or /opt/parasoft/test/9.5/eclipse.ini)
    2) Lower the value of the -Xmx option. For example, if the file contains -Xmx1024m, change it to -Xmx768.
    3) Save the file and start up the Parasoft product.
    4) If the error persists, go back to the eclipse.ini file (step 1) and lower the -Xmx value again. Repeat this process until the the Parasoft tool starts successfully.