# New Test Configuration From test tabs screen, you can create your tests related to your projects by clicking the "Create a new test" button. Or you can use "Add" button to create a test. When creating your tests, first you need to select your test type. There are four types of tests: Quick Start, HTTP Builder, Postman Collection Runner, Jmeter test.

1. **Quick Start** If you select quick start, after entering the request name, URL and selecting maximum user and total duration, you can start the run without the need for another configuration.

2. **HTTP Builder** Enter the request name. Select request type (GET, POST, PUT, PATCH, DELETE). Enter URL information. If necessary, enter the header and body fields. Save the request or add a new request if you want.

3. **Postman Collection Runner** You need to install .json and environment files. The system converts these files to jmx files and saves them as requests.

4. **Jmeter Test** You should upload your files in jmx format. At least one JMeter file must be added. Supported Plugin List:\ JMeter Web Socket 1.0.2 - JMeter Web Socket 1.2.10 - MSSQL JDBC 11.2.1 - Loadmance GRPC 1.1 - Loadmance WebRTC 1.1 - Loadmance WebRTC 1.1 - BZM HLS 3.1 - BZM Parallel Sampler 0.12

After selecting the test type and uploading the necessary files, you should configure your test. You can specify your settings as custom in the configuration or you can use pre-sets by choosing our template. The details of the templates are summarized below. **Custom:** If you select the custom feature, in the screen that opens, enter the engine count and iteration. It can make one or more volumes. On volumes, enter the target user per engine, duration, ramp up and ramp down values. **Linear:** If you select Linear Test template, enter engine count and iteration values. It has a single volume at the bottom. And then enter target user per engine and duration values. The duration value is always equal to the ramp-up value. **Load:** If you select Load Test template, enter engine count, iteration, virtual user per engine and total duration values. It has a single volume at the bottom. The ramp-up and ramp-down values are equal to 1/20 of the total duration. The load test cannot exceed 2 hours. **Endurance:** It is the same as the load test, only its duration is longer than 2 hours. **Peak:** If you select Peak Test template, enter engine count, iteration, virtual user per engine, total duration and also peak count values. The peak test is calculated based on the entered values and reflected in the graph. **Stress:** If you select Stress Test template, enter engine count, iteration, virtual user per engine, total duration and also stress count values. The stress test is calculated based on the entered values and reflected in the graph. The stress count must be at least 3. The descriptions of the other terms in the configuration field are as follows: **Ramp Up:** It is the time to reach the maximum number of users in the test. **Ramp Down:** It is the time to decrease from the maximum number of users to 0 users. **Volumization:** By setting up your test flow in a voluminous structure, you can distribute different loads at different times. In template usage, the volumization values are determined by the system. **KPI:** By adding KPIs to your samplers, providing conditions, and tracking values, you can monitor the performance of your test.

**DNS Override:** You can override existing DNS information by entering new DNS details (host name and IP).

**Network Type:** By changing your network type, you can adjust your run speed.

**Geolocation:** In this section, you can select the geographic locations from which your performance tests will run. You can configure your test engines by choosing either Cloud or Private option. In both Cloud and Private options, you can see the "Required Engines" and "VU per Engine" values that show the resource requirements for your test. In the Cloud option, after selecting a location such as Stockholm, SE, you can specify how many engines to use in the Engine Count field on the right. To add multiple locations, use the "+ Add Geolocation" button. Remember to save your geolocation information after making all your selections. Distributing your test load across multiple geographic locations helps simulate real-world traffic patterns and identify performance issues that may only appear under specific regional conditions.

In the Private mode, you'll see your available engines with their status information. Each engine displays its name, online status, last seen timestamp, and both public and private IP addresses. You can select these private engines for your tests by clicking on them. Use the "Manage Engines" option to add, remove, or configure your private test engines.

**Global Variable:** You can set global variable values that are suitable for your test.

After making your KPI, DNS override, network type, geolocation and global variable settings, you can check your test if you want, or save it to run later. If you want to run it immediately, you can start the test right away by clicking the "Run Test" button.

At this stage, it may take a few minutes for the machines to be ready. After the machines are ready, the test will start. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://loadmance.gitbook.io/loadmance/documentation/new-test-configuration.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.