chore(boxes): adding react frontend tests#4824
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. Join @signorecello and the rest of your teammates on |
Benchmark resultsMetrics with a significant change:
Detailed resultsAll benchmarks are run on txs on the This benchmark source data is available in JSON format on S3 here. Values are compared against data from master at commit L2 block published to L1Each column represents the number of txs on an L2 block published to L1.
L2 chain processingEach column represents the number of blocks on the L2 chain where each block has 16 txs.
Circuits statsStats on running time and I/O sizes collected for every circuit run across all benchmarks.
Tree insertion statsThe duration to insert a fixed batch of leaves into each tree type.
MiscellaneousTransaction sizes based on how many contracts are deployed in the tx.
Transaction processing duration by data writes.
|
c8cd2ad to
02b1e10
Compare
e6bae66 to
4c25499
Compare
294ef15 to
62aae1f
Compare
|
Indeed, that was one of the reasons for the refactor in the first place. We had all sorts of things in boxes. In this case it was decided that boxes would contain a minimal e2e so they can be in sync with the monorepo. Thanks for the review! |
Docs PreviewHey there! 👋 You can check your preview at https://65e223057dacf100a6f97788--aztec-docs-dev.netlify.app |
8dce181 to
b9776ba
Compare
6f8d3f6 to
b9e13a8
Compare
b9e13a8 to
f6e439f
Compare
Merge activity
|

This PR adds a frontend test for the react box