Use Zeta Test Management in the web application

The web application provides browser-based workflows for Zeta Test Management. It complements the Windows client but does not provide identical functionality. Use this page to understand the documented web areas, perform a test run in the browser, and choose the correct access path for administration or setup.

Before you start, obtain the web address, an active user account, access to the intended project, and confirmation of which configurable preview areas are enabled for your environment and role.

Core areas and configurable preview areas

In the currently documented Zeta Test Management 5.2 scope, test runs and result search are web core areas. The following additional areas are configurable preview functionality:

  • requirements (requirements);
  • test library (test-library);
  • performed tests (performed-tests);
  • reviews (reviews);
  • reports (reports);
  • backup (backup);
  • test variants (test-variants).

Preview areas are globally disabled by default. Global activation alone does not make every area visible: individual area settings, user roles, project permissions and project features also apply. Review the Windows, web and MCP capability matrix before planning a rollout.

Perform a test run in the browser

  1. Open the HTTPS address supplied by your administrator and sign in with your assigned account.
  2. Select the intended project and open the test-runs area.
  3. Choose the planned test run and the test case assigned to you. Read the instructions and expected result before recording the outcome.
  4. Record the actual result and status, save your work, and continue with the next test case available to your role.
  5. Use result search to verify recorded outcomes when this is part of your workflow.

If a project, test run or action is missing, do not assume that data has been deleted. Ask an administrator to check the account, project membership, role, licence, project features and enabled web areas. Use the Windows client for project setup, comprehensive administration and workflows not explicitly available in the web application.

Installation and other access paths

Web users need only the HTTPS address and an authorised account. Server installation, certificates, project paths, database access and preview-area configuration remain administrative responsibilities.