Get started
This guide is designed for newcomers to DogQ who want to get started with the no-code testing platform. Learn how to create and execute your first test.
Last updated
Was this helpful?
This guide is designed for newcomers to DogQ who want to get started with the no-code testing platform. Learn how to create and execute your first test.
Last updated
Was this helpful?
If you haven't created an account yet you can visit our Registration page to sign up. If you plan to work in a team, you will be able to invite your colleagues once you've created and verified your account.
Upon logging in for the first time you will be greeted with an invitation to engage in an onboarding demo. Take a moment to complete it, it can help you get your hands on the application and understand how it works faster.
Once you've logged in, go to Dashboard or Projects page and can click on the "New Project" button to create your first Project.
By clicking on the "New Project" button, you will be forwarded to the Project creation page. Give your first project some meaningful name and click Save - we'll skip the other features for now.
Project is the central entity of DogQ and is at the top of the organization hierarchy. It contains lower-level entities Modules. Let's click on "New Module" to create one.
A Module may represent an actual module of your app or just be a Test Suite, depending on how you organize your workflow. Modules contain scenarios that you can execute individually or schedule in batches and then monitor the results in real-time For demo purposes, we will be creating a simple test of a button used to access the DogQ Sign Up form, so we'll call the Module "Authorization". Enter the name and click Save.
After creating the Module you will be redirected right into it, then you can start writing your first Scenario.
The Scenario is an actual Test Case within the DogQ. It contains a set of automated steps that you define. Scenarios can be scheduled in groups or executed on an individual basis.
Having created "Authorization" Module, you can click on the "New Scenario" button. You will need to specify the Scenario name, click save and you will be redirected to your newly created Scenario.
If you make a step back, you'll see the page with all Scenarios in the specific Module ("Authorization" in this case). On this page you can check the latest status of your Scenario (Status), see the number of Steps within the specific Scenario (Steps), and the overall number of this scenario executions within DogQ (Runs).
At the "Log In" Scenario page let's add the first step now - you can do this by clicking on the "Add Step" button.
You can view different step types used within the Scenario by opening "Select Type". A full description of the available test steps is here.
For our first Scenario, let's open the DogQ home page, click on the "Get Started" button and validate that after doing so we're navigated to the registration form. As with all tests, the first thing we need to do is add Go to URL step and enter the address (https://dogq.io).
Now let's simulate a click on the "Get Started" button. For that we need to add a Click element step and provide a Locator (find more info on different locators here). In this case let's simply use the button label ("Get Started").
And finally we want to confirm that clicking on the "Get Started" button prompts us to the Sign Up form at a specific URL. Let's add an assertion and enter the URL we expect to be at.
You can find the current execution status inside the Test Runs block in the top-right corner of the Test Editor or on the dedicated Executions page that you can access from the Sidebar.
Depending on the execution progress, Scenarios obtain one of the following statuses:
Once the test run is complete, inside Executions you can click on "Details" on any individual execution to see what tests were run (if multiple) as well as their step-by-step reports.
Click on the button to immediately initiate a Test Run.
Pending - Scenario execution started. You can also monitor the completion percentage.
Passed - All steps completed successfully.
Failed - One of the execution steps failed.