update docs

Author: skudasov

book/src/SUMMARY.md

@@ -44,7 +44,6 @@
   - [Performance]()
   - [Chaos]()
 - [Interactive](framework/interactive.md)
-- [Continuous Integration](ci/ci.md)
 - [Libraries](./libraries.md)
   - [Seth](./libs/seth.md)
   - [WASP](./libs/wasp.md)

book/src/ci/ci.md

@@ -51,7 +51,6 @@ type Config struct {
 func TestDON(t *testing.T) {
 	in, err := framework.Load[Config](t)
 	require.NoError(t, err)
-	pkey := os.Getenv("PRIVATE_KEY")
 
 	// deploy anvil blockchain simulator
 	bc, err := blockchain.NewBlockchainNetwork(in.BlockchainA)

book/src/framework/components/blockchains/anvil.md

@@ -17,8 +17,6 @@ For example, to integrate with remote `k8s` environment you can use `CTF_CONFIGS
 
     [[blockchain_a.out.nodes]]
       # set up your RPC URLs
-      docker_internal_http_url = "http://anvil-2cfcf:8545"
-      docker_internal_ws_url = "ws://anvil-2cfcf:8545"
       http_url = "http://127.0.0.1:8545"
       ws_url = "ws://127.0.0.1:8545"
 
@@ -34,7 +32,6 @@ For example, to integrate with remote `k8s` environment you can use `CTF_CONFIGS
 
   [data_provider.out]
     # setup your data provider URLs
-    base_url_docker = "http://host.docker.internal:9111"
     base_url_host = "http://localhost:9111"
 
 [nodeset]
@@ -49,8 +46,6 @@ For example, to integrate with remote `k8s` environment you can use `CTF_CONFIGS
 
       [nodeset.out.cl_nodes.node]
         # set up each node URLs
-        docker_internal_url = "http://node0:6688"
-        p2p_docker_internal_url = "http://node0:6690"
         p2p_url = "http://127.0.0.1:12000"
         url = "http://127.0.0.1:10000"
 

book/src/framework/components/external.md

@@ -59,3 +59,7 @@ Spin up your `Blockscout` stack
 ctf bs up
 ```
 More [docs](observability/blockscout.md)
+
+## Interactive
+
+If you're a non-technical user or want to integrate with Chainlink using a language other than Golang, please follow our Interactive [setup](interactive.md) guide.

book/src/framework/getting_started.md

@@ -33,6 +33,8 @@ Allow it to run in `System Settings -> Security Settings` (OS X)
 ```
 ./ctf b ns
 ```
-Press `Ctrl+C` to remove the stack.
+Use `Tab/Shift+Tab` to select an option, use `<-`, `->` to change the option, `enter` to submit.
+
+Press `Ctrl+C` to remove the services.
 
 ![img.png](images/interactive-node-set.png)

book/src/framework/interactive.md

@@ -1,10 +1,22 @@
 ## Framework
 
-The Framework module a lightweight, modular, and data-driven framework designed for combining off-chain and on-chain components while implementing best practices for end-to-end system-level testing:
+The primary focus of the Chainlink Testing Framework is to reduce the complexity of end-to-end testing, making complex system-level tests appear straightforward.
+It enables tests to run in any environment and serves as a single source of truth for system behavior as defined by requirements.
+
+### Features
+- **Straightforward and sequential test composition**: Tests are readable and give you precise control over key aspects in a strict step-by-step order.
+
+- **Modular configuration**: No arcane knowledge of framework settings is required; the config is simply a reflection of the components being used in the test. Components declare their own configuration— `what you see is what you get`.
 
-- **Modular configuration**: No arcane knowledge of framework settings is required; the config is simply a reflection of the components being used in the test. Components declare their own configuration—'what you see is what you get.'
 - **Component isolation**: Components are decoupled via input/output structs, without exposing internal details.
+
 - **Replaceability and extensibility**: Since components are decoupled via outputs, any deployment component can be swapped with a real service without altering the test code.
-- **Caching**: any component can use cached configs to skip setup for faster test development.
+
+- **Quick local environments**: A common setup can be launched in just `15` seconds 🚀 [*](#cached).
+
+- **Caching**: Any component can use cached configs to skip setup for even faster test development.
+
 - **Integrated observability stack**: get all the info you need to develop end-to-end tests: metrics, logs, traces, profiles.
 
+###### * If all the images are cached, you are using [OrbStack](https://orbstack.dev/) with M1/M2/M3 chips and have at least 8CPU dedicated to Docker
+

book/src/framework/overview.md

@@ -9,6 +9,16 @@
 
 These tests act as a maturity model and are implemented across all our products.
 
+Run them locally:
+```
+CTF_CONFIGS=smoke.toml go test -v -run TestSmoke
+CTF_CONFIGS=load.toml go test -v -run TestLoad
+CTF_CONFIGS=chaos.toml go test -v -run TestChaos
+CTF_CONFIGS=upgrade_some.toml go test -v -run TestUpgradeSome
+```
+
 Use this [workflow](https://github.com/smartcontractkit/chainlink-testing-framework/actions/runs/11739154666/workflow?pr=1311) as a starting point for developing a new end-to-end integration test.
 
-Set the count to 5-10 during development, and once stable, set the timeout and proceed to merge.
+Set the count to 5-10 during development, and once stable, set the timeout and proceed to merge.
+
+If you need to structure a lot of different tests (not only end-to-end) follow [this](https://github.com/smartcontractkit/.github/tree/main/.github/workflows) guide.

book/src/framework/testing.md

@@ -2,13 +2,13 @@
 
 The Chainlink Testing Framework (CTF) is a blockchain development framework written in Go. 
 
-Its primary purpose is to help Chainlink developers create extensive integration, e2e, performance, and chaos tests to ensure the stability of the chainlink project.
+Its primary purpose is to help Chainlink developers create extensive integration, e2e, performance, and chaos tests to ensure the stability of the Chainlink project.
 
-It can also be helpful to those who just want to use chainlink oracles in their projects to help test their contracts, or even for those that aren't using chainlink.
+It can also be helpful to those who just want to use Chainlink oracles in their projects to help test their contracts, or even for those that aren't using Chainlink.
 
 This documentation is primarily for:
-- Developers looking to write end-to-end tests
-- Quality Assurance Engineers aiming to test locally
+- Engineers looking to write end-to-end tests
+- Non-technical users or external developers who want to [setup](framework/interactive.md) `Chainlink` nodes locally
 
 To get started with writing tests, refer to the [Framework](./framework/getting_started.md) chapter, where we guide you from basic to more complex scenarios.