Overview

Create a project

 

 

Note: As soon as you create your first project, you'll be directed to the test cases tab of that project. To view any created projects, click on your profile in the bottom-left corner and click Home.

Note: A single project can accommodate multiple test cases grouped into different modules, but they usually are subsets of the same use case. Different projects are ideally meant to carry out testing of essentially different use cases. For example, to test two different products or to serve the requirements of two different teams.

Project Navigation Bar

 

• Dashboard - The Dashboard provides a quick view of useful information, such as Project Health, Analysis of Test Runs, Failed Cases, Failure Root Causes, and other such key metrics which can be visually tracked for analysis.
  
  
• Test Cases - Test cases contain information about an action or a function that is being tested. You can select a platform -  Web Browser, Android, iOS or API, for each test case, and options will be provided based on the selection. For example, iOS or Android test cases will let you drag and drop tasks for device actions or interactions such as double-tap, long press, swipe, along with many other actions. A test case for Web Browser will offer Form Actions, Browser Actions, Keyboard and mouse actions, and many other tasks using simple scripts. An API test case will let you add request URLs, the request method, assertions to validate API calls, and options to add variables for Header, Status code, and Body.

Different modules can be created to categorize test cases. For example, "Module A" can have "Test Case 1" and "Test Case 2", while "Module B" can have "Test Case 3" and "Test Case 4". 

• Test Suites - To automate test cases, they have to be bundled into a Test Suite. You can group test cases into a Test Suite and choose the order in which the cases are to be executed - parallel execution or in a sequence.
  Continuing the example from the previous point, "Test Case 1" and "Test Case 4" (belonging to different modules) can be grouped into a Test Suite called "First Test Suite". You can then configure how or when "First Test Suite" should be run using Test Plans. Statistics of execution results are also displayed in Test Suites.

• Test Plans - This is where you specify automation details for test suites. Details like the owner of the test run, agent for test execution, and environments in which the test must run are set up in this section. You can also select the run frequency, test start date and time, and also the days on which the test suite must run.  You can also set up notifications to be triggered at various events. For example, when the test starts, completes or fails. Overall result notifications are also supported for third-party applications.

• Results - Here you can view the high-level results of your test runs. For example, the number of runs, count of runs that are complete or running, and the success rate of your Test Plans. Detailed information of a Test Plan, such as the number of test cases that have passed, failed, or are running, the duration of test case runs, and details of the response, can be viewed inside each Test Plan result.

• Users - You can add multiple users to a project. They can perform various operations in the project based on the assigned profile.

• Settings 
  
• Create variables to store global values or environment-specific values.
  
• Add new elements to store the locators for the actions performed for various test cases.
  
• Save files used in your test cases.
• Tunnel to integrate your local network to Zoho QEngine's cloud
  
• Zoho QEngine agent to run test cases locally in your machines.

• Profile - You can navigate back home to access the other projects created or the other projects/portals shared. Manage your Zoho account by clicking on My Account; to log out from the account, click Logout.

Agents

Note: The agent is optional to use, and is needed only when you want to run tests locally on your machine. You can also simply use the default agent that comes with Zoho QEngine if running tests on the cloud is not a concern, in which case you do not need to have an agent installed.