Projects & configuration
A project holds everything you test for one app. Its configuration says where the tests run (environments) and on what (browser profiles).
Create a project
Owners, Admins and Testers can create projects. On the Projects page, each row's menu has Edit and Delete.
The Configuration tab
Open Materials → Configuration. It has four sections:
| Section | What you set |
|---|---|
| Project settings | Project name, description, and New cases start as: Steps, Gherkin or Free text |
| Environments | The sites a plan can run against, with their access entries |
| Browser profiles | The browsers, window sizes and devices tests run on |
| Execution time limit | How long one execution may take before it is stopped |
Click Save settings to keep changes to the project settings.
Environments
An environment is a site to test, such as Staging or Production. Click New environment and enter a Name and a Base URL. You choose the names; there are no fixed environments.
- Each plan runs against one environment. Quick runs and schedules ask you to pick one.
- Each environment gets a key made from its name. The editor shows it, for example "Plans select it as "staging"". Renaming an environment changes its key, so plans that used the old key no longer find it: open those plans and choose the environment again.
- Deleting an environment moves it to the Trash for 30 days. Meanwhile, plans that run against it will not find it.
Access entries
Some sites need something before the first page loads: a session cookie, an item in local storage, a request header or basic authentication. Add these under Access in the environment. The types are Cookie, Storage item, Header and Basic auth.
- Qalion sets them by code before the test opens its first page. The AI is told their names, never their values.
- Values are stored encrypted and never shown again. A saved entry reads "Unchanged · set …". Type a new value to replace it.
- An entry is applied on the environment's own host. A test on another environment that reaches this host finds it prepared too.
Browser profiles
A browser profile is what a test runs on: a browser, a window size and, for phones and tablets, the device. Every project starts with six profiles: Chrome (the default), Edge, Firefox and Safari on a 1920×1080 desktop, plus Galaxy S24 Ultra and iPhone 15 Pro Max.
Click New profile to add one:
| Field | Values |
|---|---|
| Start from | A device (iPhone 15 Pro Max, 15, 14 or SE; Pixel 7 or 5; Galaxy S24 or S9+; iPad Pro 11, iPad or iPad Mini; Galaxy Tab S9 or S4) or a desktop size. It fills in the rest; you can adjust it. |
| Family | Desktop, Tablet or Mobile |
| Engine | Chromium, Firefox or WebKit |
| Browser | Google Chrome, Microsoft Edge, Chromium, Firefox or Safari (WebKit) |
| Width, Height | 240 to 3840 pixels |
| Pixel ratio | 1 to 5 |
| Mobile emulation | On or off. Firefox has no mobile emulation. |
| Touch screen | On or off |
| Enabled | Disabled profiles are skipped by runs |
| Default for new cases | The profile new plan rows start on |
| User agent, locale and time zone | Optional overrides |
- A project can hold up to 50 profiles.
- A profile that a plan or a past result uses can't be deleted. Disable it instead; history keeps its name.
Execution time limit
Limit per execution sets how long one execution may run, from 2 to 30 minutes. The default is 15 minutes. An execution that goes over ends as Error with the reason Timed out.
Longer limits let slow flows finish, but a stuck test holds a browser session and spends credits until it stops. A run keeps the limit that was set when it started. Owners, Admins and Testers can change it.
Delete a project
Deleting a project moves it to the Trash, with all its folders, test cases, plans and runs. You can restore it from Trash → Deleted projects for 30 days.
Was this page helpful?