Projects and applications

A project holds the applications you test, and each application holds its versions. Test cases, elements, test data, and everything else you author belong to one application version.

Create a project

1. Click Create New and select Project.

2. Enter the Project Name and an optional Description.

3. To hold more than one application, select Allow adding multiple applications in this project. Click Add Application, select the Application Type, and enter a Name. A project holds a single application by default.

4. To hold more than one version per application, select Allow multiple versions for applications.

5. Click Create.

Note

Custom fields defined under Settings > Custom Fields > Projects appear on this dialog.

To edit a project, go to Project > Project Settings. The Edit Project dialog updates the project details, the multiple applications and versions settings, the project members, the test case types, and the requirement types. Click Update to save.

To switch projects, click the current project on the Dashboard, select the Project, Application, and Version, then click Go to project.

Execution engines

Testsigma runs tests on 2 engines, Classic and Modern. Modern waits for elements and for the page state before it interacts with them, which reduces timing-related failures, and it handles Shadow DOM and web components more natively than Classic.

You select the engine when you create an application, and the engines on offer depend on the application type.

Application type	Available engines
Web application	Classic and Modern
Unified (Android and iOS)	Modern
Android	Classic
iOS	Classic
Mobile Web	Classic
Salesforce	Classic
REST API	Classic
Desktop	Classic
Windows	Classic

Note

The engine cannot be changed after you create the application. To use a different engine, create a new application. Your existing tests stay as they are.

Note

When an application type supports more than one engine, the selection appears only if engine selection is enabled for your account. Otherwise Testsigma applies the default engine for that application type and the selection does not appear. Contact support@testsigma.com to have it enabled.

Addons are engine-specific. A Classic addon is written in Java and a Modern addon in TypeScript, so moving one to the other engine means rebuilding it.

Manage applications

Applications live under Project Settings > Edit Project > Applications.

Note

The Applications tab is hidden while a project holds a single application. To show it, edit the project and allow multiple applications.

To add an application, click New Application, enter the Application name, Description, and Version name, select the Application type, and click Create.

To edit one, select it from the dropdown, make the changes, and click Update.

To delete one, select it from the dropdown, click Delete Application, enter DELETE, and click Delete.

Note

Deleting an application destroys every version in it, along with the test cases, test data, and uploads in those versions.

Manage application versions

A version keeps one line of tests separate from another. If you have 10 tests against version 1.0.0 and a beta build is in development, copy the version, rename the copy to 1.0.0-beta, and add the beta tests there. Work on 1.0.0-beta leaves the tests in 1.0.0 untouched.

Versions live under Project Settings > Edit Project > Versions.

1. Click New version.

2. Enter a Name, an optional Description, and the Start Date - End Date.

3. (Optional) Turn on Copy Data from Previous Versions and select the models to carry forward.

4. Click Create.

Note

Multiple versions are available only if Allow multiple versions for applications was selected when the project was created.

To edit or delete a version, click the ellipsis icon ⋮ next to it and select Edit Version or Delete Version. Deleting asks you to enter DELETE and click I understand, delete this.

To find a version’s ID, hover over the version name and click Copy.

Requirements

A requirement is a condition or capability the application has to meet, and mapping test cases to requirements is how you track coverage against them. A requirement is functional, non-functional, or domain.

Requirements are created from a test case, not from project settings.

1. Open a test case and click Manage Test Case in the utility panel.

2. Click Create New in the Requirement field.

3. Enter a Name and an optional Description.

4. Select the Type.

5. Select the Start Date and Completion Date.

6. Click Create.

To edit one, expand the Requirement field in Manage Test Case and click Edit.

Project settings

Three lists in Project > Project Settings classify test cases. Each is per project, and Testsigma supplies defaults for all of them. They feed the filters on the test case library and the grouping in run results, which is what makes them worth maintaining.

List	Defaults	What you can change
Requirement types	Customer Requirements, User Interface Requirements, Functional Requirements, Non-Functional Requirements	Add, rename, and delete
Test case types	Functional, non-functional, integration, and others	Add, rename, and delete
Test case priorities	Critical, Major, Medium, Minor	Nothing. The defaults are fixed

Note

New priorities can no longer be added. The 4 defaults remain available.

To add a requirement type or test case type, open Project Settings, click Requirement Types or Test Case Types, click Add Type, type the name in the blank row, and press Enter. To rename one, hover over it, click Edit, change the text, and press Enter. To delete one, hover over it and click Delete.

Note

A type cannot be deleted while a test case still uses it. Click View Test Case in the confirmation dialog and reassign those test cases to another type first, then delete the type by entering DELETE.

Save points

A save point stores the state of a whole project: its test cases, elements, test data profiles, and step groups. Restore one to roll the project back to that state. Testsigma stores a maximum of 10 save points at a time, and importing test cases creates one automatically.

To create a save point, go to Save Points, click Create Save Point, enter a name, and click Create. A save point opens in a new tab, so you can check its contents before you use it. From its ellipsis icon ⋮, you can edit its note or delete the save point by entering DELETE.

Note

Restoring a save point replaces the project’s current test cases, elements, test data profiles, and step groups with the versions the save point holds.

To restore a save point, click Restore on it, enter RESTORE, and confirm.

Delete a project

Note

Deleting a project destroys every application and application version in it, along with all of its test cases, elements, test data profiles, custom functions, uploads, requirements, test suites, test plans, run results, and environments.

1. Go to Project > Project Settings.

2. Click Delete.

3. Enter DELETE and click Delete in the Delete project dialog.

4. Enter DELETE and click Delete at the Delete project prompt.

Frequently asked questions

Can I use both engines in the same account?

Yes. Each application carries its own engine, so Classic and Modern applications run side by side. The choice is permanent per application, not per account.

Is the Classic engine being discontinued?

No. Classic has no planned end date, and some application types run on Classic only.

Is the Modern engine a beta?

No. Modern is a production engine. Its coverage is still expanding across application types, which is why some types run on Classic today.

What do I gain from the Modern engine?

Modern waits for elements and for the page state before it interacts with them, which reduces timing-related failures. It also handles Shadow DOM and web components more natively than Classic.

Does the engine change how I author tests?

No. The low-code editor, the recorder, and AI-assisted generation work the same on both engines. The engine affects execution only. The one exception is AI Step, which is available on Classic and not currently on Modern.

Do my Classic addons work on the Modern engine?

No. Classic addons are written in Java and Modern addons in TypeScript, and the 2 are not interchangeable. Moving an addon to Modern means rebuilding it in TypeScript.