Last Active
  • Clean Parasoft Registry for dotTEST Visual Studio Plugin

    When installing a new version of Parasoft on Visual Studio, it is recommended to remove the old version with the uninstaller since we can only have one version of Parasoft on Visual Studio.

    However, if the uninstallation is completed but when installing a new version of Parasoft, a error message displays that "Cannot install Parasoft Test 9.5 for Visual Studio into the main Visual Studio configuration because there are other installed products that are not compatible with the current version. Please uninstall Parasoft Test 9.0 and try again." This indicates the uninstallation is unsuccessful and we will need to clean the Parasoft registries to make sure nothing left from the previous version of the Parasoft tool.

    In this case, please follow the below steps to completely remove C++test and/or dotTEST from the current machine.

    If both C/C++test for Visual Studios and dotTest are installed, please remove both tools as well as the following procedure will affect both products.
    Please move the following directories in file system:
    For Visual Studio 2010:
    {Visual Studio 10.0 install dir}\Common7\IDE\Extensions\Parasoft\Test
    {Visual Studio 10.0 install dir}\Common7\IDE\Extensions\Parasoft\DotTest
    {Visual Studio 10.0 install dir}\Common7\IDE\Extensions\Parasoft\CppTest

    C++test/Parasoft Test/dotTest installation directories

    Default location for 32bit system are:
    C:\Program Files (x86)\Parasoft\C++test for Visual Studio\9.x
    C:\Program Files (x86)\Parasoft\Test for Visual Studio\9.x
    C:\Program Files (x86)\Parasoft\dotTest\9.x

    Please remove all registries in the following list:
    On x64 machines:

    HKLM\SOFTWARE\Wow6432Node\Parasoft\Test for Visual Studio\9.0
    HKLM\SOFTWARE\Wow6432Node\Parasoft\C++test for Visual Studio\9.0



    On x86 machines

    HKLM\SOFTWARE\Parasoft\Test for Visual Studio\9.0
    HKLM\SOFTWARE\Parasoft\C++test for Visual Studio\9.0



    On both architectures for VS2010:

    {Microsoft Visual Studio 10.0 install dir}\Common7\IDE\Extensions\Parasoft\TestCenter
    {Microsoft Visual Studio 10.0 install dir}\Common7\IDE\Extensions\Parasoft\Test
    {Microsoft Visual Studio 10.0 install dir}\Common7\IDE\Extensions\Parasoft\DotTest
    {Microsoft Visual Studio 10.0 install dir}\Common7\IDE\Extensions\Parasoft\CppTest

    All Visual Studio versions, x64:
    HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\Parasoft dotTEST_is1
    HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\Parasoft Test 9.0 for Visual
    HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\C++test 9.0 for Visual

    All Visual Studio versions, x86:
    HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Parasoft dotTEST_is1
    HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Parasoft Test 9.0 for Visual Studio_is1
    HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\C++test 9.0 for Visual Studio_is1

    Please perform a find in the registry list and look for "Parasoft" and remove all Parasoft related Registry (ignoring SOAtest/Virtualize related folders)
    You can now install the newer version of Parasoft successfully.

  • Using LoadTest Continuum in DevOps delivery pipeline

    Running performance tests as a part of the continuous delivery pipeline is becoming a best practice in DevOps environments. You can start integrating performance tests into the continuous delivery pipeline by adding selected performance tests to Jenkins or a continuous integration tool of your choice and having them run regularly. Depending on your needs you can run performance tests at one or more of the following points in the build/test infrastructure:

    After each build with a reduced set of performance “smoke” tests.
    Once a day with a more comprehensive set of performance tests.
    Once a weekend or based on infrastructure availability with a set of long running tests for endurance testing or high volume load tests for stress testing.
    This by itself, however, is not enough. Manually analyzing load test reports can be time consuming and may require special skills not every developer possesses. Without the ability to automate load test report analysis, reviewing performance test results becomes a tedious time sink. Vital performance information may also get overlooked. In such scenarios you may be running performance tests continuously, but the benefit of them will be limited.

    To get the full benefit of continuous performance testing you need to set up an effective mechanism to analyze performance test results. LoadTest and LoadTest Continuum (LTC) provide you with tools that help automate performance tests results collection and analysis and give you insights into the performance of your application. The following steps will help you set up your environment for continuous performance test execution with LoadTest and LoadTest Continuum:

    Review and configure LoadTest project QoS metrics for automation.
    Deploy and configure LoadTest Continuum for load test report collection.
    Configure LoadTest projects into batches for execution.
    Start running LoadTest project batches as a part of continuous integration, and use LoadTest Continuum to regularly review and analyze performance test results.
    Review and Configure QoS Metrics for Automation

    LoadTest Quality of Service (QoS) metrics are one of the key features for automating the analysis of performance test results. QoS metrics reduce large amounts of data in a load test report to a set of success/failure answers about your application performance. LoadTest offers a rich set of QoS metrics that range from ready-to-use threshold metrics to custom scripted metrics that allow you use the LoadTest API for advanced load test data analysis.