Execute test cases

Execute and get report automated test results through implemented reporters. Add reporter to test automation project and get results no matter it’s local, remote or CI\CD execution. Keep all manual and automated test runs in one place with merging capabilities.

Real Time report test case run

Reducing the time required to develop and test software is one of the primary goals of modern Agile teams. We take our customers’ wishes into account. That’s why we have included the Execute test cases feature in TMS, with extensive capabilities for launching manual and automated tests. Test execution through an intelligent test management tool saves time and increases testing efficiency and software quality.

How to work with the feature?

When you enter any project in tesomat.io test management you will see many folders with tests that need to be passed. They can be manual or automated. The tester manually runs the first ones, and upon completion, they give a Passed/Failed/Skipped status and leave a comment. The latter is run from the terminal using Advanced Reporter if they are created in any test automation framework.

Let’s consider the Execute test cases function on the example of a Mixed Run, a test run that contains both types of tests. In this case, the user’s algorithm will be as follows:

  1. Go to the Runs page.
  2. Click the menu button in the upper right corner and select Mixed Run.
  3. Run all tests or a separate Test Plan.
  4. Select the desired CI service (e.g., Azure) and test environment (browser and OS) from the drop-down lists.
  5. Assign a name to the test run.
  6. Click Launch.

Please note: If there are only manual tests in the test plan, the smart system will immediately turn Test Run into manual, which means users will see the tests that need to be passed in Manual Test Execution mode.

Additional features when using the Execute test cases function

After testing has been started, you will find yourself on the page where testing is directly performed. Here there is a variety of convenient functionality. You can:

  • Edit test plans before starting a test or even while running a test.
  • Filter tests by their status.
  • Change the presentation of tests. They can be grouped in a list or as a tree – nested in suites.
  • Enable multi-select mode and select multiple tests.
  • Assign a status to several tests at once.

In addition, when we run manual test cases our test management system has the following:

  • Progress bar – visually shows the current ratio of tests in different statuses. This is very convenient for managers. For example, when launching large-scale testing before release, managers need to understand how many tests are passed/failed/skipped and how many are Not Run yet. Just click on this button, and the tests that should be given attention in the first place will be filtered. This is an indispensable feature on projects with a lot of tests.
  • Priority filtering – this feature is very important because almost all projects use test prioritization. They are assigned a level of importance Low, Normal, or High. Again, this is convenient for managers. They can see what status the High Priority tests are in. If any fail, the release is delayed until the defect is fixed. This makes it possible to make predictions and plan the team’s work.
  • Toggle description – we have already mentioned that the Execute test cases function allows you to run tests in Checklist mode, i.e., without displaying descriptions. If you need to see them, just click on the Toggle description button, and you will immediately see the description and test steps.
  • Comment field – under the buttons for assigning status to tests, there is a comment field. It is convenient that the system has templates of frequently used comments. That is, the user does not need to constantly write them manually. In addition, you can add your own templates. This saves a lot of time.
  • Make changes to Test Run – you can add test run participants or increase the number of tests during testing. This is convenient when you have already realized after the start of testing that you need to test additional functionality. With this feature, you don’t need to create a new test run but can edit an existing one.
  • Report on current status – of the test run you can see the progress of the test by pre-grouping the tests by suite or in a list format, as well as filtering them by status.
  • Analytics – the Test Runs page displays key analytical metrics, including the number of tests in each test run, test execution progress by bar, Passed Failed Skipped test ratios, etc.

At the end of the test run, the user needs to click the Finish button, after which all data will be saved, and a Report will be generated. Thus, the Execute test cases feature allows you to efficiently manage test cases, run manual and automated tests simultaneously, and track their results. This saves time for the QA team and allows you to release a high-quality product to the market faster.

Other test management features that will make using Execute test cases even more efficient:

  • Test executions by step – if the test has prescribed steps, not just a description, you can assign a status to each. These statuses are saved until the end of the test run, and the manager can see exactly where the error occurred. As a result, it becomes clear that it is necessary to start a defect in a certain functionality and fix it.
  • Checklists – allows you to create checklists of test tasks, i.e., to document your actions without describing them in detail. When you start a test run, you can choose in which mode to do it. If you set the switch to Checklist mode, all test case descriptions will be hidden. This is very useful in situations where testers constantly run the same tests (for example, smoke testing) and do not want to be distracted by a screen with descriptions that are familiar to them.
  • CI\CD execution – such executing test cases allows you to run automated tests, manual tests, and both types of tests simultaneously – in Mixed Run mode. When working with automated tests, the user can go to the CI service in use and see what stage the test is at. In this case, all the statuses of automated tests will be displayed in Testomat.io.
  • Rerun automated tests manually – sometimes to check particularly important tests or if the results of the automated test are unreliable, you may need to run auto-tests manually. To do this, just select the test you want and click Relaunch manually.
  • Jira integration – the Jira Plugin allows you to set up two-way integration of the TMS with the bug tracking system. Thanks to this function, you can run test scripts directly from Jira. Moreover, even non-technical experts can do this.
  • Rerun failed tests – in addition to the individual automatic tests, you can also set up a manual mode for failed tests. To do this, select the desired tests and check the Relaunch Failed on CI checkbox. The system will re-run the failed tests and display their results.