[docs] Improve docs on chip-tool tests. Add example. Fix broken links.

docs/guides/chip_tool_guide.md

@@ -657,6 +657,26 @@ In this command:
 
 -   _<test_name\>_ is the name of the particular test.
 
+#### Example: running TestClusters test
+
+As an example of running one test suite test:
+
+```
+# Clean initialization of state.
+rm -fr /tmp/chip_*
+
+# In a shell window, start the DUT device.
+./out/debug/standalone/chip-all-clusters-app
+
+# In a second shell window, pair the DUT with chip-tool.
+./out/debug/standalone/chip-tool pairing onnetwork 1 20202021
+
+# Now run the test
+./out/debug/standalone/chip-tool tests TestCluster --nodeId 1
+```
+
+Developer details on how the test suite is structured can be found [here](../../src/app/tests/suites/README.md).
+
 ### Parsing the setup payload
 
 The CHIP Tool offers a utility for parsing the Matter onboarding setup payload

src/app/tests/suites/README.md

@@ -246,10 +246,10 @@ Top level key to define a YAML test: [test](#property-test)
     [tests.js](../../../../examples/placeholder/linux/apps/app1/tests.js)
 
 -   chip-tool(darwin) tests:
-    [tests.js](../../../../examples/chip-tool-darwin/templates/tests.js)
+    [tests.js](../../../../examples/chip-tool-darwin/templates/tests/tests.js)
 
 -   chip-tool tests:
-    [tests.js](../../../../examples/chip-tool/templates/tests.js)
+    [tests.js](../../../../examples/chip-tool/templates/tests/tests.js)
 
     ```javascript
     // Manual test definitions. Does not run in CI.