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
In issue #172 we documented a note of the initial difficulties of implementing this:
However we did not add notes from our meeting with Jason, but our assumption about the need to generate multiple scenarios was indeed affirmed.
Note about multiple input handling / advanced transaction builder:
Earlier we mentioned that we're not sure how multiple inputs can be tested at once, since there can only be one 'slot' field in a >scenario. We'll have to discuss this with Jason, but our expectation is that we'd need to generate multiple scenarios, one for each >input, and check that they all pass.
However, we noticed that our scenarios do support P2PKH inputs, which are evaluated separately. So it does seem like it's >possible to evaluate multiple inputs using multiple scripts. We will need to look into this further.
Today we started looking at @kiok46's new PR. We extracted his example file into an automated test with documented output. We looked through the output template, which all looks to be correct. We did notice that some tests from the "regular" libauth template fixtures were failing (likely due to naming convention changes), and there were TypeScript issues surrounding the breaking changes.
We also want to further investigate if we can minimise the breaking changes to the TransactionBuilder API and we will need to merge the new TransactionBuilder file with the existing one, and the new LibauthTemplate file with the existing one as well.
Next session we want to expand the test cases a bit by adding more contracts and more configurations of inputs/outputs (e.g. multiple inputs spending with the same function). Then we want to start refactoring / merging the new and existing files as mentioned above.
When we are doing refactors, it will be good to also see if we can address these issues while doing so: #204
We should also update the tests under e2e/transaction-builder to use Mocknet with the new debugging functionality.
No description provided.
The text was updated successfully, but these errors were encountered: