Get rid of 'runTests' command

Author: hawkeyexl

docs/get-started/actions/checkLink.md

@@ -173,7 +173,7 @@ Consider the following test configuration, which checks the validity of `https:/
 To run the test, use the following command:
 
 ```bash
-npx doc-detective runTests -i bad-certificate.json
+npx doc-detective -i bad-certificate.json
 ```
 
 This command executes the test, but it fails, returning the following response:

docs/get-started/create-your-first-test.md

@@ -78,7 +78,7 @@ To create your first test, follow these steps:
 5. In your terminal, enter the following command to run the test:
 
    ```bash
-   npx doc-detective runTests --input homepage-check.spec.json
+   npx doc-detective --input homepage-check.spec.json
    ```
 
    By default, Doc Detective scans the current directory for valid tests, but you can specify your test file using the `--input` argument. For more information, see [Run tests](/docs/get-started/sample-tests.md#run-tests).

docs/get-started/sample-tests.md

@@ -14,49 +14,40 @@ npm i
 
 ## Run tests
 
-To run your tests, use the `runTests` command:
-
 ```bash
-npx doc-detective runTests
+npx doc-detective
 ```
 
 By default, Doc Detective scans the current directory for valid tests, but you can specify your test file with the `--input` argument. For example, to run tests in a file named `doc-content-inline-tests.md`, run the following command:
 
 ```bash
-npx doc-detective runTests --input doc-content-inline-tests.md
+npx doc-detective --input doc-content-inline-tests.md
 ```
 
 To customize your test, file type, and directory options, create a `.doc-detective.json` [config](/docs/references/schemas/config) file. If a `.doc-detective.json` file exists in the directory when you run the comment, Doc Detective loads the config. Otherwise, you can specify a config path with the `--config` argument.
 
 ```bash
-npx doc-detective runTests --config .doc-detective.json
+npx doc-detective --config .doc-detective.json
 ```
 
 **Note**: All paths are relative to the current working directory, regardless of the config file's location.
 
 You can override config options with command-line arguments. For example, to run tests in a file named `tests.spec.json`, even if that isn't included in your config, run the following command:
 
 ```bash
-npx doc-detective runTests --config .doc-detective.json --input tests.spec.json
+npx doc-detective --config .doc-detective.json --input tests.spec.json
 ```
 
-### Run remotely hosted tests
+<!-- ### Run remotely hosted tests
 
 You can run tests hosted remotely by specifying the URL of the test file with the `--input` argument. For example, to run tests from a file hosted at `https://doc-detective.com/sample.spec.json`, run the following command:
 
 ```bash
-npx doc-detective runTests --input https://doc-detective.com/sample.spec.json
+npx doc-detective --input https://doc-detective.com/sample.spec.json
 ```
 
 These tests run the same way as local tests, but Doc Detective fetches the test file from the specified URL and stores it in a temporary directory. The URL must be accessible to the machine running the tests.
-
-## Check your test coverage
-
-You can check the test coverage of your documentation source files with the `runCoverage` command, specifying the source file or directory of source files with the `--input` argument. Doc Detective identifies potential areas of test coverage with file-format-specific regex, and supports CommonMark syntax natively. If you want to test coverage of a file with different syntax, update your the `fileTypes` object of your [config](/docs/references/schemas/config) file accordingly.
-
-```bash
-npx doc-detective runCoverage --config .doc-detective.json --input doc-content.md
-```
+ -->
 
 ## Next steps
 

docs/get-started/tests/index.md

@@ -138,7 +138,7 @@ To search for American Shorthair kittens,
 
 ### Detected tests
 
-Doc Detective can automatically generate tests based on your documentation source files and your `fileTypes` configuration. Detected tests are useful for large, complex test suites that you want to keep in sync with your documentation. Test detection works by setting `runTests.detectSteps` to `true` and defining markup patterns and associated actions in the `fileTypes.markup` array in your [config](/docs/references/schemas/config), which Doc Detective uses to extract steps from your doc source files. You can define multiple test patterns in your config to extract different types of tests from your documentation.
+Doc Detective can automatically generate tests based on your documentation source files and your `fileTypes` configuration. Detected tests are useful for large, complex test suites that you want to keep in sync with your documentation. Test detection works by setting `detectSteps` to `true` and defining markup patterns and associated actions in the `fileTypes.markup` array in your [config](/docs/references/schemas/config), which Doc Detective uses to extract steps from your doc source files. You can define multiple test patterns in your config to extract different types of tests from your documentation.
 
 Detected tests are useful for keeping your tests in sync with your documentation. When you update your documentation, Doc Detective automatically updates the tests based on the new content. Detected tests are generated automatically. You can't edit detected tests directly, but you can update your config or documentation source files to change the tests.