e2e

Lava E2E

If you wish you can also run E2E tests independently

Lava Protocol E2E

go test ./testutil/e2e/ -run ^TestLavaProtocol$ -v -timeout 1200s

Lava SDK E2E

If this is the first time you run the e2e after fetching a branch and you didn't compile the protobufs first run:

(Make sure that GOPATH is defined in your environment)

Init and build the SDK:

cd ecosystem/lava-sdk
./scripts/init_sdk.sh -s
yarn build
cd -

Build lavajs:

cd ./ecosystem/lavajs
yarn e2e-setup
cd -

Now you can run the test running:

go test ./testutil/e2e/ -run ^TestLavaSDK -v -timeout 1200s

Or, In one line:

yarn --cwd ./ecosystem/lava-sdk/ build; yarn --cwd ./ecosystem/lavajs/ e2e-setup; go test ./testutil/e2e/ -run ^TestLavaSDK -v -timeout 1200s -test.count=1

notice test.count is added to prevent cache from forming

Run all our E2E using the following command (from the root) {NOT STABLE}

yarn --cwd ./ecosystem/lava-sdk/ build; yarn --cwd ./ecosystem/lavajs/ e2e-setup;
go test ./testutil/e2e/ -v -timeout 1200s

This E2E performs the steps below to test if the system is working as expected.

1. Start lava in developer mode (equivalent to running the command "ignite chain serve" ).
2. Check if lava is done booting up by sending a GRPC request.
3. Send Spec and Plan proposals and stake providers and clients.
4. Check if the proposals and stakes are properly executed.
5. Start the JSONRPC Proxy.
6. Start the JSONRPC Provider.
7. Start the JSONRPC Gateway.
8. Check if the JSONRPC Gateway is working as expected by sending a query through the gateway.
9. Start the Tendermint Provider using the running lava process as RPC.
10. Start the Tenderming Gateway.
11. Check if the Tendermint Gateway is working as expected by sending a query through the gateway.
12. Start the REST Provider using the running lava process as RPC.
13. Start the REST Provider.
14. Check if the REST Gateway is working as expected by sending a query through the gateway.
15. Send multiple requests through each gateway.
16. Check if a gateway responds with an error.
17. Check if payments are paid.
18. Start lava in emergency mode.
19. Wait until downtime and 2 virtual epochs will be passed.
20. Send requests to check that max CU was increased.

After the steps above are finished (even if a step fails and the E2E ends) the E2E will save all the captured logs.

Allowed Error List

The allowed error list contains a list of errors that is allowed to happen during tests. The key is the error substring that can be seen in the logs. The value is the description on why this error is allowed.