> For the complete documentation index, see [llms.txt](https://docs.dogq.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dogq.io/documentation/workflow-tips.md).

# Workflow tips

Clicking on **Gear Wheel** ⚙️ next to the name of your Project, Modules or Scenario, you can configure additional features to optimize your workflow. 

Cross-browser settings can also be adjusted via **Schedule** in dropdown menu on Projects, Modules, Scenarios pages.

### Cross-browser testing

With DogQ Cross-browser testing feature you can run tests in multiple browsers simultaneously. Here's what it looks like inside Project Settings:

<figure><img src="/files/M5YJOQ14opYi2UbmLjR7" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Right now only 3 browsers are available, the rest are in our roadmap.
{% endhint %}

These settings can be adjusted at every level and are inherited, i.e. custom settings of a Module will be inherited by Scenarios inside it, regardless of what Project settings are.&#x20;

<figure><img src="/files/0518fW5HjTr3NrWdinxS" alt="" width="563"><figcaption></figcaption></figure>

When you execute or schedule a Scenario, a separate test run is created for each browser you have selected. In this example we have Test A with only Chrome and Test B with both browsers selected, take a look at the test runs. Each one has a browser icon next to its name to indicate what environment it was run in, allowing you to easily navigate the records.

<figure><img src="/files/0BxVFtbZuB6CwJHS4rg4" alt=""><figcaption></figcaption></figure>

#### Scheduling settings

When scheduling tests you can specify browsers that will be used for that particular scheduling session, regardless of the Project-level settings.&#x20;

***

### 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.&#x20;

{% hint style="info" %}
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, Slack notifications settings affect the whole Team.
{% endhint %}

<figure><img src="/files/21W0fu2qJ1kHCjgKj62j" alt=""><figcaption></figcaption></figure>

#### 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.

Check out the following article to learn how to [Connect Slack](https://docs.dogq.io/documentation/integrations/slack).

### 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**.

<figure><img src="/files/GHisg6bxFMgRJrenzTaT" alt=""><figcaption></figcaption></figure>

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](/documentation/macros.md). 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.

***

### Browser extensions support

DogQ allows you to upload browser extensions you would like to test or in case it is required by the testing conditions. In the **Extensions** tab of Project Settings you can provide browser extensions in a form of [CRX](https://docs.fileformat.com/plugin/crx/) files, that will be installed before every test run.

<figure><img src="/files/5GJwj2jmUsqvoJ58ev5x" alt="" width="563"><figcaption></figcaption></figure>

***

### 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.

<figure><img src="/files/DUOXHPvwO2bOgi2AMYrw" alt=""><figcaption></figcaption></figure>

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.&#x20;

<figure><img src="/files/A2T7ZGnXfqTlk4YkeRJc" alt=""><figcaption></figcaption></figure>

Naming them with prefixes like "01", "02" will place them in a numerical order.&#x20;

<figure><img src="/files/BB4MkS2WUGc5E9TqY0cS" alt=""><figcaption></figcaption></figure>

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.

<figure><img src="/files/0QTfmNCrh3fKqZ9EZBVu" alt="" width="375"><figcaption></figcaption></figure>

***

### Exporting Projects as PDF

You can create a PDF out of an entire Project with all the tests inside it. Exporting your projects as PDFs can be useful for boosting collaboration and communication in your team as PDF files are very portable, easy-to-share lists of tests that can be viewed by anyone you send them to.&#x20;

To use this:

* click the <img src="/files/oqP91vjTsj7FJeKfnVgc" alt="" data-size="line"> button at the top of the Modules list on the Project Show page&#x20;
* or via the actions dropdown menu&#x20;

<figure><img src="/files/mx8QyBAp9MWyeZFOJdpf" alt=""><figcaption></figcaption></figure>

***

### Navigating with search bar&#x20;

In DogQ you can quickly find and navigate to any Project, Module or Scenario instantly by searching for its name, description, or step value. The search field can be accesed from anywhere - it's in the top-left corner of the work area, right next to the sidebar logo.

<figure><img src="/files/SC7mbZDJ30UnlmZPutrD" alt=""><figcaption></figcaption></figure>

To locate the test or Project/Module you're seeking, you can search by:&#x20;

* Scenario/Module/Project name
* Scenario description
* Step description
* Step value

This feature becomes especially handy once your list of tests has grown to a certain extent or you simply prefer to navigate your suite using test names and/or descriptions.&#x20;

As you type into the search field, an autocomplete dropdown will appear with Scenarios, Modules and Projects that match your input.

<figure><img src="/files/FWmawgEQUe5eZx2gtL0b" alt=""><figcaption></figcaption></figure>

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.dogq.io/documentation/workflow-tips.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.