Project

Overview

The Project section allows specifying the NeoLoad project definition. The Project definition can be declared with servers, variables, User Paths, Populations and Scenarios composing the project.

Definition

Definition has several top-level keys:

Name	Description	Accept variable	Required	Since
name	The root key defining the name of the project	-	✓
includes	The definition of as code files to be included	-	-	6.10
sla_profiles	The definition of SLA profiles	-	-	6.9
variables	The definition of variables	-	-
servers	The definition of servers	-	-
user_paths	The definition of virtual User Paths	-	-
populations	The definition of Populations	-	-
scenarios	The definition of Scenarios	-	-
project_settings	The definition of project preferences	-	-

Example

Below is an example of a NeoLoad project:


name: MyProject
sla_profiles:
- name: MySlaProfile
  thresholds:
  - avg-request-resp-time warn >= 200ms fail >= 500ms per test
  - perc-transaction-resp-time (p90) warn >= 1s fail >= 2s per test
  - error-rate warn >= 2% fail >= 5% per test
  - error-rate warn >= 5% per interval
variables:
- file:
    name: products
    path: data/list_of_products.csv
servers:
- name: mypc
  host: mypc.intranet.company.com
user_paths:
- name: MyUserPath
  actions:
    sla_profile: MySlaProfile
    steps:
    - request:
        url: http://www.company.com/select?name=${products.col_0}
    - think_time: 1s
    - request:
        server: mypc
        url: /valide
populations:
- name: MyPopulation
  user_paths:
  - name: MyUserPath
    distribution: 100%
scenarios:
- name: MyScenario
  populations:
  - name: MyPopulation
    constant_load:
      users: 500