simplify compat env

Author: skudasov

book/src/framework/nodeset_compatibility.md

@@ -1,6 +1,6 @@
 # Chainlink Node Set Compatibility Testing Environment
 
-The difference between this and [basic node set configuration](nodeset_compatibility.md) is that here you can provide any custom configuration for CL nodes.
+The difference between this and [basic node set configuration](nodeset_environment.md) is that here you can provide any custom configuration for CL nodes.
 
 Create a configuration file `smoke.toml`
 ```toml
@@ -78,69 +78,13 @@ Create a configuration file `smoke.toml`
       user_secrets_overrides = ""
 ```
 
-Create a file `smoke_test.go`
-```golang
-package capabilities_test
-
-import (
-	"fmt"
-	"github.com/smartcontractkit/chainlink-testing-framework/framework"
-	"github.com/smartcontractkit/chainlink-testing-framework/framework/components/blockchain"
-	"github.com/smartcontractkit/chainlink-testing-framework/framework/components/fake"
-	ns "github.com/smartcontractkit/chainlink-testing-framework/framework/components/simple_node_set"
-	"github.com/stretchr/testify/require"
-	"os"
-	"testing"
-)
-
-type Config struct {
-	BlockchainA        *blockchain.Input `toml:"blockchain_a" validate:"required"`
-	MockerDataProvider *fake.Input       `toml:"data_provider" validate:"required"`
-	NodeSet            *ns.Input         `toml:"nodeset" validate:"required"`
-}
-
-func TestDON(t *testing.T) {
-	in, err := framework.Load[Config](t)
-	require.NoError(t, err)
-	pkey := os.Getenv("PRIVATE_KEY")
-
-	bc, err := blockchain.NewBlockchainNetwork(in.BlockchainA)
-	require.NoError(t, err)
-	dp, err := fake.NewFakeDataProvider(in.MockerDataProvider)
-	require.NoError(t, err)
-	out, err := ns.NewSharedDBNodeSet(in.NodeSet, bc, dp.BaseURLDocker)
-	require.NoError(t, err)
-
-	t.Run("test something", func(t *testing.T) {
-		for i, n := range out.CLNodes {
-			require.NotEmpty(t, n.Node.HostURL)
-			require.NotEmpty(t, n.Node.HostP2PURL)
-		}
-	})
-}
-```
+You can reuse `smoke_test.go` from previous [setup](nodeset_environment.md)
 
 Run it
 ```bash
-go test -v -run TestNodeSetCompat
-```
-
-You'll see something like, use any URL to access CL node
-```bash
-6:14PM INF Chainlink node url URL=http://127.0.0.1:34041
-6:14PM INF Chainlink node url URL=http://127.0.0.1:34045
-6:14PM INF Chainlink node url URL=http://127.0.0.1:34044
-6:14PM INF Chainlink node url URL=http://127.0.0.1:34042
-6:14PM INF Chainlink node url URL=http://127.0.0.1:34043
-```
-
-Use credentials to authorize:
-```
-[email protected]
-fj293fbBnlQ!f9vNs
+go test -v -run TestNodeSet
 ```
 
 Summary:
 - We deployed fully-fledged set of Chainlink nodes connected to some blockchain and faked external data provider
-- We understood how we can test different versions of Chainlink nodes for compatibility
-- We explored the Chainlink node UI
+- We understood how we can test different versions of Chainlink nodes for compatibility and override configs