Test in collaborative mode

With the following recommendations, the members of a test project can work easily and efficiently in collaborative mode. They reduce significantly the number of potential conflicts that the team members may face.

Designing Collaborative Tests

A collaborative test project is composed of elements shared for the Virtual Users, shared Containers, variables, populations, servers, monitors, preferences of the project, and Load Generators zones.

The process to design a test project includes several steps. A major step consists of defining one or more Virtual Users with other shared elements like servers, variables, and so on.

  1. When NeoLoad 6.3 is installed on the same machine as the collaboration server, it is necessary to ensure localhost is not used as the hostname of the remote server.
  2. It is advised to assign one or more design steps to every member of the team. It is necessary to prevent several members work on the same Virtual User, the same population, the same zone, the same monitored machine, or the same scenario.
  3. Every member on a shared project must refrain from working on the design steps assigned to the rest of the team. This prevents conflicts. The members of the team should work on their Virtual Users only.
  4. It is advised to share a project on its first design version (first record in general). Creating shared resources, such as servers, is performed by one team member. This prevents naming conflicts from occurring. Once the version is posted, the other team members can retrieve it and contribute to it consecutively.
  5. Deleting elements of other members must be approved by their designers.
  6. Regular updates of the project are very useful to identify as early as possible potential conflicts induced by forgetful team members.
  7. Each time a project is updated, it is strongly advised to use the Project Sanity Check wizard to identify any missing element in the project.
  8. Similarly, publishing a project must be performed whenever possible.
  9. A project must always be updated before it is published. Updating a project may well help revise it, plan corrective actions, prevent conflicts, and so on.
  10. Actions performed when solving conflicts may be difficult to understand, all the more as NeoLoad must process a large number of conflicts. When the update wizard identifies one or more conflicts, team members are advised to close the wizard and duplicate the shared Virtual User or Container showing the conflicts. Team members can perform backups of their work to make sure elements are not unexpectedly deleted by the conflicts resolution process.
  11. Before launching a test, it is useful to check the consistency of a shared design with the Project Sanity Check described in Check the sanity of a project at design time. Updating a project may have created inconsistencies after, for instance, deleting elements which are required by a Virtual User.
  12. Before launching a test with a collaborative scenario, the Execution Sanity Check wizard may detect any missing element which may corrupt or block the test. It is necessary to correct any issues raised, as described in Check the test sanity before execution.
  13. Tagging a project is strongly advised to lock some versions of the project as soon as it proves sensible to do so (project milestone, test campaign, archiving, and so on).