You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: plans/README-plans.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ This workflow uses Testing Farm's Github Action [Schedule tests on Testing Farm]
21
21
22
22
## Running Tests
23
23
24
-
You can run tests locally with the `tmt try` cli or remotely in Testing Farm.
24
+
You can run tests locally with the `tmt try` cli or remotely in Testing Far.
25
25
26
26
### Running Tests Locally
27
27
@@ -32,7 +32,7 @@ You can run tests locally with the `tmt try` cli or remotely in Testing Farm.
32
32
2. Optionally modify environment variables to, e.g. run only specified test playbooks by modifying `SYSTEM_ROLES_ONLY_TESTS`.
33
33
4. Enter `tmt try -p plans/test_playbooks_parallel <platform>`.
34
34
This command identifies the `plans/test_playbooks_parallel.fmf` plan and provisions local VMs, a control node and a managed node.
35
-
5.`tmt try` is in development and does not identify tests from URL automatically, so after provisioning the machines, you must type `t`, `p`, `t` from the interactive prompt to identify tests, run preparation steps, and run the tests.
35
+
5. tmt try is in development and does not identify tests from URL automatically, so after provisioning the machines, you must type `t`, `p`, `t` from the interactive prompt to identify tests, run preparation steps, and run the tests.
0 commit comments