You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: TESTING.md
+16Lines changed: 16 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -72,6 +72,10 @@ To request a cluster test to be run on your PR, comment on your pr `/cluster_tes
72
72
for a basic test or a hard-migration test respectively. After commenting, reach out to the
73
73
[Splice Contributors](CONTRIBUTORS.md) to approve and trigger the actual test on your behalf.
74
74
75
+
### Enabling the new Canton bft ordering layer
76
+
77
+
If you want to run the integration tests with the new Canton bft, you can do so by including the message `[bft]` in your commit message.
78
+
75
79
## Running Tests Locally
76
80
77
81
### Managing Canton for Tests
@@ -208,6 +212,17 @@ No installation of `lnav` is required, as it is provided by default by our `dire
208
212
Documentation about common pitfalls when writing new integration tests and debugging existing ones can be found [here](/apps/app/src/test/scala/org/lfdecentralizedtrust/splice/integration/tests/README.md).
209
213
If you wish to extend our testing topology please also consult [this README](/apps/app/src/test/resources/README.md) about name and port allocation.
210
214
215
+
### Enabling the new Canton bft ordering layer
216
+
217
+
If you want to run the integration tests locally with the new Canton bft, canton must be started with the `-e` flag.
218
+
This can be done by running `./start-canton.sh -we`.
219
+
Furthermore the integration test must run with the `SPLICE_USE_BFT_SEQUENCER` environment variable set to `true`.
0 commit comments