@@ -17,18 +17,26 @@ $ make zetanode
17
17
18
18
This Makefile rule builds the zetanode image. ** Rebuild if zetacored/zetaclientd code is updated** .
19
19
``` bash
20
- # in zeta-node/
21
20
$ docker build -t zetanode .
22
21
```
23
22
24
23
### Run e2e tests
25
24
26
25
Now we have built all the docker images, we can run the e2e test with make command:
27
26
``` bash
28
- # in zeta-node/
29
27
make start-e2e-test
30
28
```
31
29
30
+ #### Run admin functions e2e tests
31
+
32
+ We define e2e tests allowing to test admin functionalities (emergency network pause for example).
33
+ Since these tests interact with the network functionalities, these can't be run concurrently with the regular e2e tests.
34
+ Moreover, these tests test scoped functionalities of the protocol, and won't be tested in the same pipeline as the regular e2e tests.
35
+ Therefore, we provide a separate command to run e2e admin functions tests:
36
+ ``` bash
37
+ make start-e2e-admin-test
38
+ ```
39
+
32
40
### Run upgrade tests
33
41
34
42
Upgrade tests run the E2E tests with an older version, upgrade the nodes to the new version, and run the E2E tests again.
@@ -46,18 +54,22 @@ NOTE: We only specify the major version for `NEW_VERSION` since we use major ver
46
54
47
55
The upgrade tests can be run with the following command:
48
56
``` bash
49
- # in zeta-node/
50
57
make start-upgrade-test
51
58
```
52
59
60
+ The test the upgrade script faster a light version of the upgrade test can be run with the following command:
61
+ ``` bash
62
+ make start-upgrade-test-light
63
+ ```
64
+ This command will run the upgrade test with a lower height and will not populate the state.
65
+
53
66
### Run stress tests
54
67
55
68
Stress tests run the E2E tests with a larger number of nodes and clients to test the performance of the network.
56
69
It also stresses the network by sending a large number of cross-chain transactions.
57
70
58
71
The stress tests can be run with the following command:
59
72
``` bash
60
- # in zeta-node/
61
73
make start-stress-test
62
74
```
63
75
@@ -68,15 +80,14 @@ If everything works fine, it should finish without panic.
68
80
69
81
The logs can be observed with the following command:
70
82
``` bash
71
- # in zeta- node/contrib/localnet/orchestrator
83
+ # in node/contrib/localnet/orchestrator
72
84
$ docker logs -f orchestrator
73
85
```
74
86
75
87
### Stop tests
76
88
77
89
To stop the tests,
78
90
``` bash
79
- # in zeta-node/
80
91
make stop-test
81
92
```
82
93
@@ -86,7 +97,6 @@ Before starting the monitoring setup, make sure the Zetacore API is up at http:/
86
97
You can also add any additional ETH addresses to monitor in ` zeta-node/contrib/localnet/grafana/addresses.txt ` file
87
98
88
99
``` bash
89
- # in zeta-node/
90
100
make start-monitoring
91
101
```
92
102
@@ -97,7 +107,6 @@ The Grafana default credentials are admin:admin. The dashboards are located at h
97
107
### Stop monitoring setup
98
108
99
109
``` bash
100
- # in zeta-node/
101
110
make stop-monitoring
102
111
```
103
112
@@ -108,7 +117,6 @@ In addition to running automated tests, you can also interact with the localnet
108
117
The localnet can be started without running tests with the following command:
109
118
110
119
``` bash
111
- # in zeta-node/
112
120
make start-localnet
113
121
```
114
122
0 commit comments