Product scope across Windows, web, AI, and MCP¶

Zeta Test Management exposes the same governed project domain through several access paths. The Windows application and web interface both cover the full set of domain tasks in test management; the web interface adds integrated AI workspaces and browser-adapted workflows. MCP automates approved reads and writes through the same versioned domain services. Their differences primarily concern local operating-system integration and interaction patterns.

For provider setup, project chat, planning, safe actions, and Local Bridge, start with AI and automation. Detailed platform prerequisites remain under System requirements.

Product scope and access-path matrix¶

Access path	Primary purpose	Security and approval boundary
Windows client	Broad desktop editing, project administration, and local integrations	User role, project permission, licence, and selected backend model
Web application	Browser-based domain workflows, administration, project chat, quality intelligence, and AI test planning	HTTPS, authentication, roles, project features, and global or project-specific feature approval
MCP	Structured automation through approved read and write capabilities	Dedicated API key, least-privilege scopes, project context, prepare/preview/commit, and audit
Local Bridge	Controlled local Windows actions from supported web workflows	Browser extension, Native Host, website association, and an IT-managed allowlist

The exact scope depends on build, edition, licence, roles, project features, provider and scenario assignment, and administrative approval. An available access path never overrides object-level permission.

Domain tasks in Windows and web¶

Task	Web interface in version 6
Manage projects	Create/open, maintain settings and access, back up, restore, copy and transfer
Requirements and test library	Documents/chapters, units/cases, variants and quick cases, reviews, attributes, attachments, dependencies and links
Plan and perform tests	Plans, templates, packages and environments; add/synchronise cases; create, clone, perform, complete and reopen runs
Evaluate results	Search, dashboard, charts, result lists, CSV/XLSX and contextual reports
Design reports	Visual REPX designer, data queries, relations, preview, import/export and version history
Exchange data	Excel/XML, project and bug-tracker import, Word structure import for requirements, spreadsheet and attachment exports
Administration and integrations	Users/groups, LDAP, invitations, bug trackers, server settings, licence, updates and diagnostics

Start with web workflows or the existing Windows guides.

Specific access-path differences¶

Local Windows integration: browser downloads, web links and browser state replace local file dialogs and window state. Local Bridge supports approved local tools and files; free-form Lua and arbitrary user-tool command lines remain Windows features.
Report designer: external data sources use administered profiles in the web interface. Arbitrary embedded C# scripts are not executed; older custom reports may require migration.
AI and MCP: a domain workflow available in the web interface is not automatically fully executable through chat or MCP. Check the available tool catalogue, specific capability and its approval.

Regular web areas are enabled by default. Administrators can disable individual areas. AI requires separate configuration and explicit approval.

AI and safe actions¶

AI and external data egress are disabled after installation. Administrators explicitly configure provider profiles, scenarios, data zone, governance, and project permission. Chat and MCP use the same write lifecycle: prepare, review the preview, confirm, and audit.

Continue with Configure and govern AI and Safe actions, MCP and Local Bridge.

System requirements¶

The detailed current requirements are maintained on System requirements for Zeta Test Management 6.0. The dedicated page distinguishes the Windows client, local web executable, central IIS deployment, browser, database and workload sizing.

The current technical baseline is Windows x64 and .NET 10. Exact operating-system, Windows Server, IIS, browser and SQL Server versions remain release-specific support decisions and should be confirmed before production rollout.

Bug tracker integrations¶

The verified Zeta Test Management 6.0 factory registration includes connectors for:

Atlassian Jira through the REST API
Mantis
Redmine
FogBugz
Request Tracker
Pivotal Tracker

The presence of a connector does not guarantee every target-system release or operation. Before rollout, verify authentication, project selection, required and custom fields, status values, comments and attachments against a representative test instance. Confirm the supported combination with Zeta Software.

Jira authentication¶

Jira Cloud: select Basic, use the Atlassian account email address as the user name and an Atlassian API token as the password, and set Jira-IsCloudJira to true.
Jira Data Center: select Bearer and enter a personal access token in the security-token field, subject to the target version and security policy.
Custom gateway: select CustomHeader and configure the secret plus Jira-AuthHeaderName and, if required, Jira-AuthHeaderPrefix.

Use HTTPS and a dedicated technical account with least privilege. Never place real secrets in documentation or screenshots. Older documentation may name Microsoft TFS or Azure DevOps, Trac, Bugzilla or OnTime; their absence from the currently verified factory registration is not a statement about a legacy or custom integration, but they must not be planned without explicit support confirmation.