FAQ

Testomat.io frequently asked questions:

Well, I don't understand what the purpose of testomat.io is and how to use it?!

Testomat.io is a management system for automated tests. We consider a few use cases of how it may help teams and companies. Let's divide it by roles:

As QA engineer:

• Planning. You can quickly create a test suite and tests you need to check the application. Those test suites will be available for the test automation team. Once automated tests created, it can be bind with descriptions and everything will be available in one system: description, automated test implementation, test runs, attachments.
• Cooperation. You have a checklist with tests that SDET needs to automate. Test suites and descriptions can be easily created with a few clicks based on checklist support. SDET will filter a non-automated test and will start an automation. Once tests are automated you will see the corresponding status against the tests.
• Test Design. You need to describe steps in different test cases. You have steps that are reused all the time. Create steps in steps database and easily reuse it with autocompletion in test case editor.
• Test Design. You do BDD. You need to manage steps a lot so it's informative and reusable across the project. You have a central steps database where you can manage your steps for test cases.
• Development. You created a test but SDET doesn't understand what to automate. You can add steps, attachment, record, and replay sessions for SDET as assets so the test can be automated without questions.
• Maintenance. You see that automated tests are outdated and it's not catching defects in the application. You can check/review test steps and automated test implementation just in the system. The description may be updated than the automated test will be marked to be updated by SDET.
• Maintenance. SDET changed some automated tests however it's not agreed. Such a test case will be marked to be reviewed by you. You can review the description and automated test implementation simultaneously in one window.
• Cooperation. You don't need to ask SDET to provide you information about test execution, it's available right in the system.

As SDET:

• Planning. You need to create an automated test after the planning session. What exactly should be automated? Ask QA to add test suites and tests into the system so you can sort and filter non-automated tests.
• Development. You have a checklist with tests that need to be automated. You don't know exactly business logic. Create test suites and test from the checklist in the system and ask QA to write steps to a particular test to be automated.
• Agile Development. QA and SDET have the same checklist for manual testing and test automation for a sprint. QA create test cases with a description. SDET makes test automation implementation in parallel with QA. The synchronization process automatically bind a test case in the system with an automated test once it's automated.
• Development. You need to understand what overall scope of work for test automation. Once tests are created in the system you can filter necessary tests for automation by status.
• Cooperation. Your Manager and QA ask about the progress all the time. Import and synchronize automated tests with the system and provide stakeholders access to continuously track test automation without disturbing you.
• Test Execution. QA always asking about results. Give access to projects where reporting available on a continuous basis.
• Maintenance. The product team introduced changes to the application and business logic. QA changed test case descriptions. Get notifications and check easily what automated tests need to be reviewed and refactored.
• Maintenance. You have a lot of automated tests and you need to support it. You can import all your automated tests into the system and ask QA to help you monitor results, review test suites, and test to be covered by test automation.
• Management. Your manager asks you to provide more transparency to created automated tests. Import all your automated tests in a few clicks to the system and provide your manager access to it. Done. Do your next automated tests and it will be automatically synchronized with the system.

As Manager:

• Resources. You have some free resources and you would like them to help the team to complete some tasks. Assign QAs to create test suites and test cases with detailed assets for test automation for SDET to speed up the process.
• Simplicity and Transparency. You want to have one system to track test suites, test cases, steps, description, automated test implementation, results, and analytics. The system provides you all within one system with the ability to QA, SDET, and DEVs work together.
• Process. You want to align/bind your software testing and test automation processes to have synergy from it. Combine QA and SDET efforts to be responsible for whole results by using a systematic way of working.
• Reporting. No need to ask test automation team to provide your results. They run it and you check it on an ongoing basis in the reporting module
• Teamwork. You have complex application business logic. You need to have a detailed description of the test automation team before they start.

Should I edit all automated tests to bind it to testomat.io descriptions?

No. In fact, no need to edit all tests. You need to be sure the names are the same. That's all. You can import all your tests as it's and execute them, it should be matched by test names. No extra work should be done. However, there may be a case where names are different in testomat.io and source but tests should be matched than ID should be used. Check more details here https://github.com/testomatio/app/issues/133

How to allow run automated test with testomat.io reporter only in the CI?

That is implementation for Jest framework.

// inside jest.config.js
if (process.env.CI) {
  module.exports.reporters = ['default', ['./node_modules/@testomatio/reporter/lib/adapter/jest.js', { apiKey: process.env.TESTOMATIO }]],
}

Please check more details here https://github.com/testomatio/app/issues/133