summaryrefslogtreecommitdiff
path: root/pages/docs/platform/troubleshooting/tests.md
diff options
context:
space:
mode:
authorelijah <elijah@riseup.net>2016-03-04 12:32:11 -0800
committerelijah <elijah@riseup.net>2016-03-04 12:32:11 -0800
commit479dd784cec6f423feadd1cbc910105c4cd73636 (patch)
tree19ab1e920901ee1d228d9cf805e6fbcdf4da098d /pages/docs/platform/troubleshooting/tests.md
parent55565bd556790014649df80c66c49f640e9d54ac (diff)
various minor edits.
Diffstat (limited to 'pages/docs/platform/troubleshooting/tests.md')
-rw-r--r--pages/docs/platform/troubleshooting/tests.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/pages/docs/platform/troubleshooting/tests.md b/pages/docs/platform/troubleshooting/tests.md
index 383fe7b..607f924 100644
--- a/pages/docs/platform/troubleshooting/tests.md
+++ b/pages/docs/platform/troubleshooting/tests.md
@@ -8,15 +8,15 @@ At any time, you can run troubleshooting tests on the nodes of your provider inf
To run tests on FILTER node list:
- leap test run FILTER
+ workstation$ leap test run FILTER
For example, you can also test a single node (`leap test elephant`); test a specific environment (`leap test development`), or any tag (`leap test soledad`).
Alternately, you can run test on all nodes (probably only useful if you have pinned the environment):
- leap test
+ workstation$ leap test
-The tests that are performed are located in the platform under the tests directory.
+The tests that are performed are located in the platform under the tests directory.
## Testing with the bitmask client