Data model

Each request from a client to the server must contain all the necessary information to allow the server to understand the query.

The Controller receives Entry objects defined by a Status and associated to a Session containing Context information. The data model can be defined as following:

The following examples illustrate a typical request and response for creating session and entries:

Fields details

No maximum length is enforced on any string.

Note about time synchronization that to make sure the entries sent to the Controller have the appropriate timestamps, the clocks of the NeoLoad Controller, EuE platform, and all devices used must be synchronized.

Note: If a user sends an entry containing a path with a forbidden characters, then the characters will be escaped on the server side (which consists in replacing any forbidden characters with '_') and no warning message will be logged. Forbidden characters are: '£', '?', '$', '\"', '[', ']', '<', '>', '|', '*', '¤', '?', '§', ‘'µ', '#', '`', '@', '^', '²', '°', '¨'

Session

  • SessionId is a unique identification string send by the server in the response.

  • ApiKey is a string defined by the user.

  • Context: Contains the Context class objects.

Context

  • Hardware (optional): Hardware details (iPhone, Windows Phone, etc.)

  • Os (optional): OS details (iOS 7.0, Android 4.2, etc.)

  • Software (optional): Software details.

  • Location (optional): Location information.

  • Script (optional): Script information.

  • InstanceId (optional) identifies the instance.

Entry

  • SessionId is a unique identification string send by the server in the session creation response.

  • Value: Entry value.

  • Url: Uniform Resource Identifier.

  • Timestamp is an absolute time used to synchronize the entry with NeoLoad data.

  • Path is a string representing the list of nodes that contains the statistics.

  • State (optional) is an enumeration with only 2 values: PASS / FAIL.