Migrate a collaborative project

After upgrading to NeoLoad 6.7 as described in Upgrade to NeoLoad 6.7, one team member only must migrate the remote project once for all. It is advised to designate the member with the most advanced project design because, in NeoLoad 6.7, all the project components can be published on the collaboration server. The other team members will check out the remote migrated project which will overwrite their local project.

Before starting the migration process, it is necessary to pay attention to the following prerequisites:

Migrating a project 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.

EN_migrateproject

The local project migration is suspended, because the associated remote project must be upgraded beforehand to be compatible with NeoLoad 6.7. NeoLoad prompts for it being migrated.

Choosing to migrate the remote project starts the Remote Project Migration Wizard.

A click on the Next button displays the second screen of the wizard to include the test results published for the selected project in the migration process.

Clicking the Next button launches the migration process.

All the operations for the migration are executed until a message indicates that the migration is over. A click on the Finish button closes the wizard. The project on the collaboration server is now upgraded in NeoLoad 6.7.

Opening the local project again makes it possible to resume its migration. Migrating a project 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.

EN_migrateproject

Clicking Yes validates the migration process.

The tester can publish the local migrated version onto the collaboration server to share all the components which can be published in NeoLoad 6.7. For more information, see Publish a project.

The other team members must check it out to get the latest version of the project, as described in Check out locally a remote project already migrated.

  1. Ensure that:
  2. In NeoLoad 6.7, open the project.
  3. In the message box for the local project migration, click Yes.
  4. In the warning box for the remote project migration, click Yes.
  5. In the Remote Project Migration Wizard, select the project you want to migrate. Click Next.
  6. When necessary, select Design + Results to include the test results in the migration. Click Next.
  7. Wait for the migration to be processed. Click Finish.

    The project on the collaboration server is upgraded in NeoLoad 6.7.

  8. Open your local project again.
  9. In the message box for the local project migration, click Yes.
  10. When your local project is migrated in NeoLoad 6.7, you can publish it onto the collaboration server.
  11. Tell the other team members to check out the remote project.