chore(docs): update ruff in docs.

Author: spencer-tb

docs/getting_started/setup_vs_code.md

@@ -2,7 +2,7 @@
 
 VS Code setup is optional, but does offer the following advantages:
 
-- Auto-format your Python code to conform to the repository's [code standards](../writing_tests/code_standards.md) ([black](https://black.readthedocs.io/en/stable/)).
+- Auto-format your Python code to conform to the repository's [code standards](../writing_tests/code_standards.md) ([ruff](https://docs.astral.sh/ruff/)).
 - Inline linting and auto-completion (thanks to Python type hints).
 - Spell-check your code and docs.
 - Graphical exploration of test cases and easy test execution/debug.
@@ -18,38 +18,47 @@ The [ethereum/execution-spec-tests](https://github.com/ethereum/execution-spec-t
 ```text
 📁 execution-test-specs/
 └──📁 .vscode/
-    ├── 📄 settings.recommended.json
+    ├── 📄 settings.json
+    ├── 📄 settings.local.recommended.json
     ├── 📄 extensions.json
     └── 📄 launch.recommended.json
 ```
 
-To enable the recommended settings, copy the settings file to the expected location:
+By default the repository settings are applied via `.vscode/settings.json`, if you want to add your own settings please edit `.vscode/settings.local.recommended.json`.
+
+To enable the recommended launch configurations:
 
 ```console
-cp .vscode/settings.recommended.json .vscode/settings.json
+cp .vscode/launch.recommended.json .vscode/launch.json
 ```
 
-To additionally enable the recommended launch configurations:
+To additionally use and add local settings please run the following first:
 
 ```console
-cp .vscode/launch.recommended.json .vscode/launch.json
+cp .vscode/settings.local.recommended.json .vscode/settings.local.json
 ```
 
 ## Additional VS Code Extensions
 
 Open the folder in VS Code where execution-spec-tests is cloned: VS Code should prompt to install the repository's required extensions from `.vscode/extensions.json`:
 
 - [`ms-python.python`](https://marketplace.visualstudio.com/items?itemName=ms-python.python)
-- [`ms-python.isort`](https://marketplace.visualstudio.com/items?itemName=ms-python.isort)
-- [`ms-python.flake8`](https://marketplace.visualstudio.com/items?itemName=ms-python.flake8)
-- [`ms-python.black-formatter`](https://marketplace.visualstudio.com/items?itemName=ms-python.black-formatter)
+- [`charliermarsh.ruff`](https://marketplace.visualstudio.com/items?itemName=charliermarsh.ruff)
 - [`esbenp.prettier-vscode`](https://marketplace.visualstudio.com/items?itemName=esbenp.prettier-vscode)
 - [`streetsidesoftware.code-spell-checker`](https://marketplace.visualstudio.com/items?itemName=streetsidesoftware.code-spell-checker)
 - [`tamasfe.even-better-toml`](https://marketplace.visualstudio.com/items?itemName=tamasfe.even-better-toml)
 
 !!! note "Workspace Trust"
 Trust the `execution-specs-test` repository when opening in VS Code to be prompted to install the plugins recommended via the `extensions.json` file.
 
+The `.vscode/extensions.json` additionally contains a list of extensions that should be disabled:
+
+- [`ms-python.isort`](https://marketplace.visualstudio.com/items?itemName=ms-python.isort)
+- [`ms-python.flake8`](https://marketplace.visualstudio.com/items?itemName=ms-python.flake8)
+- [`ms-python.black-formatter`](https://marketplace.visualstudio.com/items?itemName=ms-python.black-formatter)
+
+Please ensure that these are disabled for the repo if they are installed as part of your VS Code extensions.
+
 ## Configuration for Testing EVM Features Under Active Development
 
 An additional step is required to enable fixture generations for features from forks that are under active development and have not been deployed to mainnet, see [Filling Tests for Features under Development](../filling_tests/filling_tests_dev_fork.md#vs-code-setup).

docs/writing_tests/code_standards.md

@@ -4,20 +4,16 @@ The Python code in the tests subdirectory `./tests` must fulfill the following c
 
 |   | Command                 | Explanation                                                              |
 |---|-------------------------|--------------------------------------------------------------------------|
-| 1 | `fname8 tests`          | Spell check passes using the `./whitelist.txt` dictionary file.          |
-| 2 | `isort tests --check --diff` | Python imports ordered and arranged according to isort's standards. |
-| 3 | `black tests --check --diff` | Python source must be black-formatted.                              |
-| 4 | `flake8 tests`          | Python lint and spell-checked.                                           |
-| 5 | `mypy tests`            | Objects that provide typehints pass type-checking via mypy.              |
-| 6 | `fill`                  | All tests must execute correctly.                                        |
-| 7 | `mkdocs build --strict` | Documentation generated without warnings.                                |
-| 8 | `pyspelling`            | Markdown spell-check.                                                    |
-| 9 | `markdownlint-cli2`     | Markdown lint check.                                                     |
+| 1 | `ruff check tests`      | Python lint, format and imports check.                                   |
+| 2 | `mypy tests`            | Objects that provide typehints pass type-checking via mypy.              |
+| 3 | `fill`                  | All tests must execute correctly.                                        |
+| 4 | `mkdocs build --strict` | Documentation generated without warnings.                                |
+| 5 | `pyspelling`            | Markdown spell-check.                                                    |
+| 6 | `markdownlint-cli2`     | Markdown lint check.                                                     |
 
-While this seems like a long list, a correctly configured editor (see [VS Code Setup](../getting_started/setup_vs_code.md)) essentially assures:
+While this seems like a long list, a correctly configured editor (see [VS Code Setup](../getting_started/setup_vs_code.md)) essentially assures that all points are mostly covered.
 
-1. Points 2 and 3 are automatically covered.
-2. Points 1, 4, 5, 8 & 9 are mostly covered. Additionally, if you skip type hints, they won't be checked; we can help you add these in the PR.
+Additionally, if you skip type hints, they won't be checked; we can help you add these in the PR.
 
 These checks must pass in order for the execution-spec-tests Github Actions to pass upon pushing to remote.