From 2dae5b962900ed8edd068dcffb15afe8d2b4acb1 Mon Sep 17 00:00:00 2001 From: Philip Offtermatt <57488781+p-offtermatt@users.noreply.github.com> Date: Wed, 6 Dec 2023 13:46:19 +0100 Subject: [PATCH] Update tests/e2e/README.md Co-authored-by: Marius Poke --- tests/e2e/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tests/e2e/README.md b/tests/e2e/README.md index 5b9a040bb6..ae04d03e0f 100644 --- a/tests/e2e/README.md +++ b/tests/e2e/README.md @@ -198,7 +198,7 @@ When something in the tests goes wrong, a nice thing about the tests is that the docker container doesn't get killed. You can sh into the docker container via e.g. `docker exec -it "testinstance" sh` and manually look around, Useful pointers are: -* Look at logs in the node homes: `/$CHAIN_ID/validator$VAL_ID` +* Look at logs in the nodes' home folder, i.e., `/$CHAIN_ID/validator$VAL_ID` * Query/Run txs on the running apps (find out the relevant addresses and node homes to use e.g. by running `htop "binaryname"`) It is also possible to locally change a step so it will *always* fail (e.g. by checking for nonsense validator balances)