System requirements for Zeta Test Management 5.2

This page summarizes the technical planning baseline for the current Zeta Test Management 5.2 line. Requirements differ between the Windows client, the local web executable, a central IIS deployment, the database and the expected workload.

The shipped product establishes Windows x64 and .NET 10 as the current technical basis. Exact Windows, Windows Server, IIS, browser and SQL Server editions remain subject to the support policy for the release you deploy. Confirm newer platform versions and special editions before a production rollout.

After checking these requirements, continue with Windows or LAN installation or central web installation under IIS.

Windows client

Platform and runtime

  • Architecture: current Zeta Test Management 5.2 builds are Windows x64 applications. Historical 32-bit installation paths are not the baseline for this product line.
  • Runtime: the Windows client targets .NET 10. The normal per-user EXE package is self-contained, so a separate .NET Framework or earlier .NET runtime installation is not required.
  • Operating system: use a maintained x64 Windows release approved for the Zeta Test Management build you deploy. Windows 11 and Windows Server 2019/2022 are relevant planning baselines for current environments. Confirm exact editions, builds, LTSC variants and newer platforms such as Windows Server 2025 with Zeta Software.

Installation, permissions and resources

  • The normal EXE setup installs for the current user and usually does not require administrator rights. Use the x64 MSI for managed endpoints or the deployment setup for a centrally maintained LAN installation.
  • The user needs the intended read and write access to project folders, attachments and the selected database. Keep application files, project data and backups in separately managed locations.
  • Size CPU, memory and local storage for project volume, attachment size, reporting and the number of concurrently opened projects. A representative pilot is more reliable than a universal minimum value.
  • Before an update, back up projects and databases, record the installed version and verify the new package's digital signature.

See Installing Zeta Test Management for the current per-user, MSI and LAN deployment paths.

Web server and browser

Deployment models

  • Central IIS deployment: the framework-dependent package zetatest-web.zip requires the matching .NET 10 Hosting Bundle with ASP.NET Core Module V2. Use a 64-bit application pool and an approved Windows Server/IIS combination.
  • Local web executable: the web EXE setup is a self-contained Windows x64 application that starts a local Kestrel instance. It is intended for evaluation or an individual local scenario, not as a replacement for a secured central IIS installation.
  • Windows Server 2019 and 2022 are relevant current planning baselines. Confirm Windows Server 2025, special editions, the precise IIS feature set and alternative reverse-proxy topologies before rollout.

Network, security and browser

  • Publish production access through HTTPS with a trusted certificate and stable DNS name. Validate the complete TLS path, redirects and forwarded headers when a reverse proxy or load balancer is used.
  • Run the application under a dedicated technical identity with only the required file and database permissions. Project files, configuration, backups and logs must not be exposed as public static files.
  • Use a current browser with JavaScript enabled. Browser support can change with product updates; confirm the required browser family and minimum version for the target release.

For the complete server procedure, see Install and configure Zeta Test Management Web. For browser features and preview boundaries, see Web application.

Database, sizing and release validation

Database, storage and capacity

  • For multi-user and web scenarios, the current documentation recommends Microsoft SQL Server 2017 or newer, including a suitable Express edition for smaller environments. Confirm the exact version, edition, compatibility level and any Azure SQL scenario for the release and expected load.
  • Keep projects, databases, attachments, configuration and backups outside replaceable application release folders. Grant only the required access and document which technical identity owns each path.
  • Plan CPU, memory, storage, database capacity and network throughput from project size, attachment volume, reports and concurrent users. Include monitoring and growth reserves instead of relying on one generic minimum.

Before rollout or update

  1. Review the release notes and confirm the intended operating-system, server, IIS, browser and SQL combination with the applicable support policy.
  2. Back up projects, databases and configuration, then perform and record a restoration test.
  3. Validate installation or update in a representative staging environment with realistic permissions and data volume.
  4. Verify sign-in, project access, one typical test run, attachments, reports, integrations and every enabled web preview area.
  5. Keep the previous application package and a matching data backup until the agreed acceptance and rollback window has ended.

Requirements from older .NET Framework, 32-bit, Internet Explorer security-zone or Code Access Security deployment models do not describe the current 5.2 line.