As usual in this life there are options, so we can run test cases
form the test cases list
from a test plan (yeah, you need to create it first)
Launching tests from test cases list
Go to the test cases section (if not there yet), and select at least one test case.
Press bulk actions button above the list of test cases.
The run command will create a tests launch. Launch requires some additional information.
Name can be omitted, then automatic name will be created based on th date.
Tags - add tags, it will help you filter the test results, i.e. if this is a smoke test launch then it is definitely worth to add smoke tag.
Issues. You can link this very launch to an issue in an issue tracker system. This is considered as advanced set-up and usage and is described outside of the quick start in Administration section.
Links. You can provide any link here with adding the description for it.
Environment defines important conditions for a launch like browser, operating system or anything else. The environment set is adjustable and you can create your own environment parameters. This is described in details in Project's description.
don't forget to Save environment.
Running the manual tests
To execute the tests in scope of the launch for the test cases you've created, you need to jump to the Launches section.
Your new launch will be on top of the list and it will contain all the information provided during creation.
Check this out!
To execute the tests you need to click launch's name and in next page jump to the Tree tab, all the stuff goes there.
Also, from the beginning:
Go to Launches
Go to your launch
Go to Tree tab
Select a test case.
Assign a test case either to yourself or to a team member (latter makes sense if you aren't a person that will perform the testing).
Follow the steps of the test.
Following the steps of a test case
You need to assign a test to yourself, otherwise you won't be able to perform any actions on the test.
Since you've assigned the test, the actions in Execution section will become available.
You need to check every step in your test and assign execution result to each step of your test.
After you completed all the steps, you need to provide your final verdict - Passed / Failed at the bottom of the page.
Closing the launch
Allure TestOps will add the data from your test launch to the analytics only after the launch is closed.
The idea behind that is the following: before you add anything that will affect your statistics, analytics, KPIs you need to check that all the data in a launch is correct. So, closing of the launch is your certification that the tests are performed properly and test results can be considered in the analytics.
Test plan creation and execution
Test plan is a group of test combined together by the logic of its creator.
That could be...
test cases used for smoke testing
only Web UI tests
Creating a test plan
This is the simplest option.
Go to the Test cases section.
Apply a filter or select test cases manually.
Click on Bulk actions button.
Select Create test plan.
Name the test plan
Jump to Test plans section an locate newly created test plan.
Further steps will be similar to ones you've made for launch when running from the test cases list.