Problem
It's currently not easy to get any visibility around computation used to perform a transction in the test framework and the best tooling currently exists via the emulator.
Suggeted Solution
Ideally something like TransactionResult.computationUsed could be provided. This way devs could write integration devs that assert that their scheduled transactions stay within acceptable bounds.
Problem
It's currently not easy to get any visibility around computation used to perform a transction in the test framework and the best tooling currently exists via the emulator.
Suggeted Solution
Ideally something like
TransactionResult.computationUsedcould be provided. This way devs could write integration devs that assert that their scheduled transactions stay within acceptable bounds.