Skip to content

Project / test project

A project (also called a test project) combines the test content with its related project files, attachments and images.

File-based components remain in the project folder. Depending on the chosen operating model, the actual test data is stored either in an embedded local database or in Microsoft SQL Server.

With SQL Server, the project folder still contains files and attachments while the database resides at the location managed by the database administrator. Back up both parts as one recoverable unit.

Check the current system requirements for release-specific database and server support.

Manage projects in the Web client

Administration → Manage projects lists projects discovered or registered on the server. This area requires a separate server administrator sign-in; a project user session is not sufficient.

  • Create new project and Open existing project link to the existing forms under Opened projects. That page also offers the standard example project.
  • Select a project and Check status to compare its database schema with this server's schema.
  • For an outdated or incompletely upgraded project, choose Upgrade project. First back up the complete project, including its database, attachments and images, and stop all other Windows, web and background clients for the project. Confirm both prerequisites and then confirm the upgrade. This may take several minutes.
  • After a successful upgrade, sign in to the selected project. If the project is newer than the server, update the application first; downgrading is not offered.
  • If the upgrade fails, check the server log and backup before retrying. An interrupted upgrade may need to be resumed.

Backup, restore, copy and export opens the existing backup page after project sign-in. Project permissions still apply. Restoring creates a new project. Before upgrading an outdated project, back it up using the previous client or your database server and file-system backup tools; the new administration page does not create an automatic backup.

Close project or Sign out ends your own web session. It does not remove access for other users or remove the project from the server's search paths. Clearing the reporting list under Opened projects does not delete project data either.

Schema upgrades deliberately require an interactive operator confirmation in the administration browser. They are not exposed through general project MCP/REST write permissions; a global MCP key does not replace this maintenance confirmation.

The upgrade runs without navigating away. A dialog shows project checking, database upgrading and result verification, followed by success or failure. If the connection fails, only status is retried, never the upgrade itself. After a server restart, the outcome may be unknown: check the project status and server log before retrying.