Your first test run¶
Start with an example project or a project you are authorised to access. A first walkthrough needs just one test case, a test plan and a recorded result.
Choose your starting point¶
| You want to … | Start here |
|---|---|
| Maintain cases, plan or perform tests in a browser | Web interface |
| Work with the installed Windows application | Windows guides |
| Install or update the software | Installation and system requirements |
| Use AI in a project | Project chat; server administrators handle configuration |
The Windows client and web application use the configured projects and permissions. Both interfaces cover domain tasks in test management; local Windows tools may require an approved Local Bridge or the Windows application. Project sign-in and server administration are separate access paths.
Practise with the example project¶
The ServiceDesk Release example contains 16 test cases with linked requirements, four test units and three test runs. Recorded passes and failures, together with sample attachments, illustrate release acceptance. The customer portal described in the tests is a fictional scenario; an executable ServiceDesk application is not included.
- Open Test case library → Requests → Create a service request and read the prerequisites, steps and expected result.
- Under Release acceptance, open the newest test run. Its initial state has four cases still open.
- Practise recording a result and an observation for an open case. Mark your entry as practice; it does not demonstrate an actual portal test.
The public demo uses German project data even when you switch the interface to English. In that project, choose Anfragen → Service-Anfrage erstellen and Release-Abnahme.
A blank project does not contain this sample data. Choose it when you want to start with your own requirements and cases.
Public online demo
Visitors to try.zeta-test.com share the same project data. Do not enter confidential or personal information, including in attachments or the AI chat. The demo resets every night at 03:30 Berlin time. It is unavailable for a few minutes during the reset. Visitors then see the original sample data again. Previous demo chats are no longer visible in the shared account. This reset does not affect your own local or self-hosted projects.
From test case to result¶
- Describe the test case. Record prerequisites, steps and the expected result. Assign the case to a test unit. Web workflow · Windows guide.
- Prepare the test run. Select the cases required for your test plan and decide what to verify. Web planning · Windows guide.
- Perform the test. Read the instructions, follow the steps and compare the actual outcome with the expected result. Windows workflow · Web workflow.
- Record the result. Save the status and your observations. Add attachments and a linked issue where your installation supports them.
- Review the results. Check the saved outcomes and use the reports available to your role. Web reporting · Windows reports.
Test library and test plan
Editing the original test case does not automatically update cases already included in a test plan. Before the next run, check whether the changed cases need to be synchronised into the plan.
If something is missing¶
If a project or action is unavailable, ask the responsible administrator to check your account, project membership, role and enabled features. Missing visibility does not necessarily mean data was deleted.
AI is optional. You can work with test cases, runs and results without it. AI suggestions do not replace domain review or a required confirmation before changes are applied.
Update an existing installation¶
Back up projects and configuration before an update. Choose the appropriate package and follow the update instructions for your deployment. The maintained version 5.2 has its own archived manual.