Links

Workflow

Understand how to perform cross-browser testing, set up notifications, use the Default First Step feature, and integrate DogQ into your pipeline with API tokens.
Clicking on Gear Wheel ⚙️ near your Projects or Modules names, you can to optimize your workflow and configure additional features. Also you can adjust cross-browser testing via Schedule in dropdown menu on Projects, Modules, Scenarios pages.

Cross-browser testing

DogQ Cross-browser testing feature allows you to execute tests in multiple environments. You can set which browsers you want your tests to be run with at every level - Project, Module and Scenario.
Right now only 2 browsers are available, the rest are in our roadmap.
When you execute or schedule a scenario, a separate test run will be created for each browser you select. Depending on the run environment, each test run is assigned by a respective icon allowing you easily navigate the records.

Notifications

Notifications can be configured in the Project settings. DogQ uses the Email of your account to send reports. Team Admins can also connect a Slack channel for DogQ to send notifications.
Please note that notifications only work for Scheduled and External executions and while Email notifications are user-specific and can be set by Team Members individually, the Slack notifications settings affect the whole Team.
Notifications options:
  • "Never" - if you don't need any notifications
  • "About any completed Test Runs" - you will receive a report that includes all scheduled and external test executions in a project, both successful and failed.
  • "About failed Test Runs" - the report you receive will again include both successful and failed runs, yet you will only get it if there are any failed executions in a project.
To connect Slack, once you have finished creating the project, go to Project Settings and click Add to Slack. This page should open in a new tab.
Provide your workspace Slack's URL and Click continue. Then log into your Slack account and complete the verification. Now you should see DogQ Notifier app requesting access to your workspace. Allow the access.
Lastly, you need to specify an ID of a Slack channel you want reports to go to. To see a channel ID in Slack you can right-click on the channel in question and select "View channel details". At the bottom there is the ID and the Copy icon.
Copy and paste the ID to the respective field in the Project Settings, choose conditions for Slack notifications and click Save.

Default First Step

With Default First Step feature you can jump-start the creation of your tests. DogQ will automatically add the first step of your choice to every new Test Scenario in the Project.
Since most of the time when you’re testing something on a site, you first need to log in, this tool really shines with a Log In Macro. Create a Macro of logging into the site you’re testing, set it as the First Default Step in Project Settings and every test you create in this project will already have the logging in part covered so you can start building the test itself without worrying about this routine precondition.

API tokens (advanced)

Also in the Project settings there is a Project Token. This can be used to integrate DogQ processes into your pipeline. For example you can automate the execution of your DogQ tests every time you deploy a new build or replace a major prod version.
To use this you need to replace "your_token" in this cURL command with the actual token:
curl --location --request POST "https://dogq.io/projects/external_execute" --header "TOKEN: your_token"
Using this token will trigger the execution of the whole Project, so if you want to only run certain tests, you will need to temporarily deactivate the rest. Project Token can be changed. Clicking on the respective button next to the token will randomly generate a new one.

Sequential Module Execution

By default when you execute an entire Module all tests in it are run more or less simultaneously. Yet there are cases when you want them to be executed in a certain order.
For example, preconditioned tests. Say, you’re testing an e-store and you need to check that clicking on a trash bin icon next to an item in a cart removes the item from the cart. So, before testing that you need the item to actually get into the cart.
You can create two separate tests, one of adding an item to the cart and of removing it.
Naming them with prefixes like "01", "02" will place them in a numerical order.
Then in the Module Settings you can turn on the Sequential Module Execution and all tests in the Module will be executed exactly in order they are in.
Last modified 24d ago