Start From Scratch

Welcome! This section guides you through the initial steps of using Testomat.io to organize and manage your testing process effectively. If you don’t have any manual or automated tests yet - follow this guide.

Create Project

Register at app.testomat.io and activate your user account. Then create a new project.

The type of your new project will influence the look of your interface, as well as its intended audience. Choose BDD Project if you plan to follow BDD descriptions or use the Cucumber framework in future. If you haven’t decided yet, you can start with default Classical Project. Depending on your choice, the interface will differ, as follows:

• Within a BDD Project, you will have feature definitions written both in the source code (by engineers) and in Testomatio (by managers and QAs). So you will be able to track and plan Cucumber automation, as well as synchronize the actual feature files with relevant test cases. When a scenario has changed in the system, but has not been updated in the code yet, you will be notified that this certain scenario is out of date.
• Within a Classical Project, test cases will be written in free form using markdown. Automated tests will be synced up with test cases, so you will be able to see the test description in one tab and the corresponding test code in another tab. When a description of a test case undergoes changes, you will be notified that a certain test might need to be updated.

Let’s start creating a project:

1. Fill the name of your project in the Project Title field.
2. The Fill demo data checkbox is optional. This option fills the project with ready-made test data so that new users can try Testomat.io quickly and easily. You can simply skip it.
3. Click the Create button to start a new project.

You have just created your first project. Now you can start creating suites and test cases for your projects.

Create Manual Test Cases

Let’s take a look at creating test cases step by step.

1. Fill the name in the input field.
2. Click the + Suite button to create a new suite.

Or another case:

Great, let’s move on! Select a certain suite to nest the creation of new test cases in that suite.

1. Select a test suite.
2. Fill the name in the input field.
3. Click the Create button to create multiple test cases.

When tests are newly created, they are marked as manual by default, which shows that they are ready for manual checks. Also, to create or edit multiple suits or test cases at once use Bulk Edit.

As a result, you can add descriptions for each test case. However, the roles of these routine test cases are clearly seen from their titles, so we can probably try to run them to verify the user management part.

Run Manual Tests

Now let’s take a look at how to run our tests and get a detailed report:

1. Select Run tab in the sidebar.
2. Click the Manual Run button to create new test run.

Before you execute your tests, you might want to specify the run environment options (a list of options is customizable) and the title for this run. In this section you will learn how to set up the environment for test execution.

3. Select the checkbox next to All Manual Tests
4. Click the Launch button to execute the tests.

You will see the list of all test cases when the test execution is launched. Mark them as passed, skipped or failed. When a test check fails, you can write the description of the failure and attach a relevant image.

Once the run is finished, the overall results of it are available for your review.

Import Automated Tests

Now let’s have a look at the import process for your automated tests. When your project is created, click the Import from Source Code button.

Or another case:

In the Import section, you are asked to pick the framework, programming language and and operating system you are using for testing.

If you don’t see the framework you work with in this list - please contact us, and we will do our best to add support for it soon!

Once you have chosen the project parameters, you will be provided with a command that you need to copy and execute in a terminal. Before running this command, please check if your environment matches these requirements:

• If you run tests in NodeJS (JavaScript, TypeScript), you should have NodeJS 10+ and npm to be installed to be able to run this command.
• If you run tests in PHP - you will need PHP > 7.2 and Composer installed.

Open a terminal, navigate to the tests folder in your project and execute the command. Seeing a report on how many tests were found means that the import command was executed successfully:

If you don’t see a similar message, this might be because our default settings do not work for you. Please check the command’s API change command parameters so it could find tests. The most common issues with import are different file naming format and/or incorrect directory for import.

When the tests are finally imported, reopen the project, and you will see that all tests with their folders and files are shown on Testomat.io.

All imported tests are marked as “Automated” by default. If you click on any of those tests, you will see its code and a link to its repository. Please, check that the link actually points to the corresponding file. Otherwise, you might want to change the repository URL in project settings.

Run Automated Tests

First, go to the Runs page, click on the Extra button and pick Setup Automated

Then you need to pick your framework from the dropdown. Testomat.io will generate instructions regarding your framework. You may need to make few changes to your code, namely, add the Testomat.io plugin.

Please note that you need to start generated commands in your terminal from your project folder.

If you have successfully launched your automated tests, a new Test Run will appear on Runs page.

Test Run Report

Click on a run to see the report. Here you can find all the important information about the completed test run. Such as the duration of the run, the performer, and so on. You can also filter by status, find specific tests by tags, or sort by available methods. Moreover, you can see tests results in real-time.

To get a detailed report of the test run, click on the Report button.

Now you can share the report with your stakeholders.

Analytics

Testomat.io Analytics provides an extensive overview of testing data by tracking both automated and manual tests. You can visualize trends over time with custom charts, identify automation coverage, monitor failure patterns, and analyze metrics like flaky or slowest tests. Additional features include a failure board, label and tag statistics for better team insights, allowing for optimized testing and proactive bug prevention.

Within the Analytics features, Automation Coverage stands out as particularly noteworthy.

Automation coverage in Testomat.io offers insights into the scope of automated testing within a project, tracking the proportion of tests that are automated versus those that remain manual. Through its analytics, Testomat.io provides a detailed view of the automated test ratio, enabling teams to identify areas that may benefit from further automation. This feature helps streamline automation strategies, making it easier to optimize test coverage in line with project goals.

For more details, refer to the Testomat.io Analytics documentation.

You’ve just scratched the surface of Testomat.io’s features. Continue reading to fully explore Testomat.io!