Upgrade to NeoLoad 2025.1

Upgrading to NeoLoad 2025.1 and its minor versions makes it possible to use the new features of the product and to upgrade the associated test projects.

Upgrading to a major version or to a minor version consists of backing up projects, installing a new version, activating the license, and upgrading projects in the new version of NeoLoad.

Note: Backing up the projects and installing the NeoLoad upgrade in its specific folder make it possible to revert back to the previous version of NeoLoad with the original projects if there are any upgrade issues.

To upgrade NeoLoad (major or minor version), follow these steps: 

  1. Make an external backup copy of your projects.

  2. Download the new version of NeoLoad.

  3. Install NeoLoad in the suggested default directory.

  4. Start NeoLoad and activate the license.

  5. Open your current projects in the new version for NeoLoad to upgrade them.

Project backup

Before migrating to NeoLoad 2025.1 and its minor versions, it is recommended to secure the projects:

  • The whole C:\Users\<user>\Documents\NeoLoad Projects\ directory can be copied in another backup directory.

  • In the NeoLoad Controller, the File > Export Project command allows generating an archive of the current project. For more information, see Export a project.

NeoLoad installation

The latest version of NeoLoad can be downloaded from the Tricentis Support Hub.

NeoLoad can be installed as described in Install the Controller.

Every major and minor version of NeoLoad is installed in a directory which is different from all other versions. It is highly recommended to use the default directory, because it makes it possible to use one version of NeoLoad or the other, until the projects are safely migrated. Although different versions of NeoLoad can be installed on the same machine, but in different directories, only one instance of NeoLoad can be started at a time.

Note: Starting from NeoLoad 7.2, installing a Linux headless version requires meeting specific requirements. For more information, see Install NeoLoad.

License activation

The installed version of NeoLoad requires a new activation of the license, for more information see Manage licenses.

Migrate projects

Migrating projects after upgrading NeoLoad is necessary to benefit from all the new functions available in the new major or minor version installed. The project migration process is fully automated. When a project is opened in NeoLoad, it detects the creation version and converts it.

Before migrating NeoLoad projects, ensure you have a backup of all projects. The automatic project up-grade is a one-way process. For more information, see Project backup.

Note: Migrating collaborative projects requires specific operations. For more information, see Upgrade a collaborative project.

Update project

When opening a project from a previous version of NeoLoad and that your project does not need to migrate, NeoLoad prompts you to update it to the latest version.

Note: The update process is not available for SVN collaborative projects.

As mentioned in the dialog box, once updated, a project can be launched with an earlier version of NeoLoad but the settings configured for the latest features will be lost when the project is saved.

Migrate framework parameters

Framework parameter definitions are stored in the conf/frameworks sub-directory of the user directory, as described in NeoLoad configuration files. Each new minor version has its own specific directory, which is created the first time NeoLoad starts.

Any framework parameters created by the user and left over from an earlier version are copied to the framework parameters directory in the new version.

Note: The frameworks created by the user are automatically migrated when NeoLoad is upgraded.

However, NeoLoad framework parameters (.NET, AMF, E Business, ICEFaces, JSF, LightStreamer, RTMP, RTMPT, Siebel, Silverlight and Workspace) do not migrate; they take their default values in the new version.

The frameworks updated by the user in an older NeoLoad version are not automatically migrated. To transfer the changes made to this type of framework, it is necessary to export the edited parameters before importing them in the new version of NeoLoad.

For more information about frameworks, see Frameworks.

Export raw data

Starting from NeoLoad 7.0, exporting raw data of test results for Transactions will result in providing rearranged data.

After exporting test results for a Transaction in .csv, the table displays new data:

  • The Time column provides the absolute time during which the container was executed.

  • The Virtual User ID column provides the Virtual User unique identifier executing the container.

  • The Success column specifies whether the Transaction executed successfully or not.

  • The Population column provides the Population the Transaction is included in.

  • The Zone column identifies the Zone used to run the test.

  • The Response time is now expressed in milliseconds.

  • The variables added as described in Transaction.