Move the todo comments and doc tests

add a recorded gif of related-tests and a textual description of
what the gif demonstrates

clients/lsp-rust.el

@@ -974,13 +974,13 @@ responds with Runnable[], while relatedTests responds with TestInfo[], which is
 over runnable. Also, this method doesn't set the `lsp-rust-analyzer--last-runnable' variable"
   (-if-let* ((resp (lsp-rust-analyzer--related-tests))
              (runnables (mapcar (lambda (runnable) (gethash "runnable" runnable)) resp)))
+             ;; TODO use dolist or some other iterator to extract all of them
+             ;; since the endpoint returns a list of hash tables that
+             ;; stores &rust-analyzer:Runnable as a value under key
+             ;; "runnable"
+             ;; we need to unpack them first
       (lsp--completing-read
        "Select test: "
-       ;; since the endpoint returns a list of hash tables that
-       ;; stores &rust-analyzer:Runnable as a value under key
-       ;; "runnable"
-       ;; we need to unpack them first
-       ;; TODO if no tests are found lsp--info with "No tests are related to this position"
        runnables
        (-lambda ((&rust-analyzer:Runnable :label)) label))))
 
@@ -995,6 +995,5 @@ https://github.com/rust-analyzer/rust-analyzer/blob/master/docs/dev/lsp-extensio
      (lsp--info "There are no tests related to the symbol at point")))
 
 
-
 (provide 'lsp-rust)
 ;;; lsp-rust.el ends here

docs/manual-language-docs/lsp-rust.md

@@ -95,10 +95,11 @@ Corresponds to [the rust-analyzer LSP extension](https://github.com/rust-analyze
 
 Corresponds to [the rust-analyzer LSP extension](https://github.com/rust-analyzer/rust-analyzer/blob/master/docs/dev/lsp-extensions.md#related-tests) 
 
-TODO record and create a gif
-   + finding obviously relevant tests
-   + calling the function on a position that has no related tests 
-![](./manual-language-docs/lsp-rust-analyzer-related-tests.gif)
+In the example below, first you see that 
+   + On the left, the function `check_infer` is defined, on the right another file is opened with many test functions, some of which call `check_infer`. With the cursor on `check_infer`, call `lsp-rust-analyzer-related-tests` and select `infer_pattern_match_slice` with fuzzy matching. The test is executed on the right with compilation major mode
+   + Move the cursor to `fn ellipsize` and attempt to find related tests to no avail. Confirm that the function is indeed untested by using swiper and finding one place in the file, where the function is called
+
+![](./manual-language-docs/lsp-rust-analyzer-find-related-tests.gif)
 
 ### Caveats