Test plan is a set of test cases aggregated using some pattern; a pattern could be a tag of a test case, belonging of a test to some feature, test suite or microservice.
Test plan allows storing the rules for grouping of tests, update the grouping, start launches for test cases combined into a test plan.
There are several ways to create a test plan, you can use the list of all test cases from Test cases section or start creating a test plan from Test Plans section.
You can tick test cases one by one, but this is quite tedious task, it's better if your tests are tagged; this will save you a considerable amount of time.
We'll use creation of a test plan to run smoke tests as an example. All the tests we use for smoke tests have the tag smoke assigned to them.
Name the test plan (Smoke tests will comply with our target).
layer = "UI Tests"
You can run tests from your test plan. There are two options to do that:
Both options will perform in the same way.
You need to click Run test plan button.
Next window will require some information to be provided. If you won't provide any data then Job on a CI server will be started with its default parameters.
<a href="some-host">Some text</a>
If you are running a test plan for a build job that contains more tests than your test plan, here is what could happen: