chore: update README.md

Signed-off-by: Tomás Migone <[email protected]>

Author: tmigone

TESTING.md

@@ -33,23 +33,38 @@ There are several types of e2e tests which can be run separately:
   - Read and write interactions with the blockchain. _Requires an account with sufficient balance!_
   - Example: a test validating that a user can add signal to a subgraph.
 
-### Hardhat local node
+### Hardhat local node (L1)
 
-To run all e2e tests against a hardhat local node run:
+It can be useful to run E2E tests against a fresh protocol deployment on L1, this can be done with the following:
 
 ```bash
 yarn test:e2e
 ```
 
-The command will perform the following actions:
+The command will:
+- start a hardhat local node
+- deploy the L1 protocol
+- configure the new L1 deployment
+- Run all L1 e2e tests
 
-- Start a hardhat node (localhost)
-- Run `migrate:accounts` hardhat task to create keys for all protocol roles (deployer, governor, arbiter, etc). This currently doesn't support multisig accounts.
-- Run `migrate` hardhat task to deploy the protocol
-- Run `migrate:ownership` hardhat task to transfer ownership of governed contracts to the governor
-- Run `migrate:unpause` to unpause the protocol
-- Run `e2e` hardhat task to run all deployment tests (config and init)
-- Run `e2e:scenario` hardhat task to run a scenario
+### Arbitrum Nitro testnodes (L1/L2)
+
+If you want to test the protocol on an L1/L2 setup, you can run:
+
+```bash
+L1_NETWORK=localnitrol1 L2_NETWORK=localnitrol2 yarn test:e2e
+```
+
+In this case the command will:
+- deploy the L1 protocol
+- configure the new L1 deployment
+- deploy the L2 protocol
+- configure the new L2 deployment
+- configure the L1/L2 bridge
+- Run all L1 e2e tests
+- Run all L2 e2e tests
+
+Note that you'll need to setup the testnodes before running the tests. See [Quick Setup](https://github.com/edgeandnode/nitro#quick-setup) for details on how to do this.
 
 ### Other networks
 
@@ -82,26 +97,4 @@ Scenarios are defined by an optional script and a test file:
    - They run before the test file.
 - Test file
    - Should be named e2e/scenarios/{scenario-name}.test.ts.
-   - Standard chai/mocha/hardhat/ethers test file.
-
-## Setting up Arbitrum's testnodes
-
-Arbitrum provides a quick way of setting up L1 and L2 testnodes for local development and testing. The following steps will guide you through the process of setting them up. Note that a local installation of Docker and Docker Compose is required.
-
-```bash
-git clone https://github.com/offchainlabs/nitro
-cd nitro
-git submodule update --init --recursive
-
-# Apply any changes you might want, see below for more info, and then start the testnodes
-./test-node.bash --init
-```
-
-**Useful information**
-- L1 RPC: [http://localhost:8545](http://localhost:8545/)
-- L2 RPC: [http://localhost:8547](http://localhost:8547/)
-- Blockscout explorer (L2 only): [http://localhost:4000/](http://localhost:4000/)
-- Prefunded genesis key (L1 and L2): `e887f7d17d07cc7b8004053fb8826f6657084e88904bb61590e498ca04704cf2`
-
-**Enable automine on L1**
-In `docker-compose.yml` file edit the `geth` service command by removing the `--dev.period 1` flag.
+   - Standard chai/mocha/hardhat/ethers test file.