ZenoTest How to – Installation, Tests & Reports

⚙️ Installation & Setup

Follow these steps to install ZenoTest and prepare your testing environment:

1. Download the latest version from our website.
2. Run the installer and follow the on-screen instructions.
3. Launch ZenoTest and create your first project.
4. Start ZenoTest via Start Menu or desktop shortcut and create a new project.

🧪 Writing Your First Test

Learn how to define your first test case, add steps, and execute it automatically.

1. Create a new Test Suite and Test Case inside ZenoTest.
2. In the 'Controls' tab, set the AUT (Application Under Test) path and optionally enable 'Start AUT autom.' to launch it automatically during recording.
3. Start the Recorder and perform the actions you want to automate—such as clicks, text entries, or selections—in your application.
4. Stop the recording. ZenoTest will list all captured UI interactions under the 'Actions' tab.
5. Review the recorded actions, deselect any unnecessary ones, and click 'Add to Code' to generate executable script code.
6. Add StartAUT(); at the beginning of your script to ensure the AUT launches when the test runs.
7. Save your project and run the test using the ▶️ Run Test button.
8. Review the execution log and the automatically generated HTML report to verify the test results.

StartAUT();
LeftMouseClick("BUTTON_1");
LeftMouseClick("BUTTON_ADD");
LeftMouseClick("BUTTON_2");
LeftMouseClick("BUTTON_EQUALS");
VerifyEqual(GetText("RESULT"), "3");
CloseAUT();
    

🎥 Using the Recorder

Record your UI actions and automatically generate reusable test code.

3.1 Starting the Recorder

• Open your project and navigate to the 'Controls' tab.
• Click the 'Record' button to launch your AUT and begin capturing interactions.

3.2 What the Recorder Captures

• Perform the actions you want to automate — ZenoTest records each relevant UI event.
• Mouse clicks (left, right, double-click)
• Mouse wheel movements (scrolling)
• Keyboard input

3.3 Finishing the Recording

• Element selections and focus changes
• When finished, stop the recording.
• Review your captured actions in the 'Actions' tab, where you can edit or convert them into script code.

💻 Generating and Editing Test Code

After recording, edit the generated C-like code to customize or extend your test logic.

4.1 Code Generation

LeftMouseClick("BTN_LOGIN");
SendKeys("TXT_USERNAME", "admin");
SendKeys("TXT_PASSWORD", "1234");
LeftMouseClick("BTN_SUBMIT");
    

4.2 Manual Editing

• Add custom logic such as conditions, variable assignments, and additional actions.
• Refactor recurring sequences and parameterize your test logic for more flexible and maintainable test cases.

4.3 Global Functions

function Login(string user, string pass)
{
    SendKeys("TXT_USERNAME", user);
    SendKeys("TXT_PASSWORD", pass);
    LeftMouseClick("BTN_SUBMIT");
}
    

📈 Viewing Reports

View test execution reports, analyze results, and monitor QA progress.

5.1 Report Contents

• Execution time and duration
• Test suite and case name
• Step-by-step results (passed/failed)
• Error messages and stack traces
• Optional screenshots on failure (future)

5.2 Accessing Reports

Reports are stored in the folder specified in the project settings and can be opened directly in ZenoTest or in your web browser.

💡 Command-Line Integration

ZenoTest supports a powerful CLI mode for automation and CI/CD workflows.

7.1 Basic Syntax

zenotest.exe -project "C:\Projects\MyProject.zproj" -suite "RegressionTests" -case "TestCase01" -report "C:\Projects\"
    

7.2 Parameters

7.3 CI/CD Integration

call zenotest.exe -run "BuildTests.zproj" -suite "Smoke" -report "C:\Reports\"
Exit codes (0 = success, -1 = failure) allow seamless integration into automated pipelines.
    

🔄 Updating ZenoTest

ZenoTest automatically checks for updates at startup and notifies you when a new version is available. Manually download the latest installer from the official website. All existing projects, settings, and reports remain preserved after updates.

🧩 Troubleshooting

Common issues and solutions to help you continue testing without interruptions.

6.1 Common Issues