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
Currently, it is not possible to perform unit testing for sponsored transactions using Simnet in Clarinet. This limitation makes it difficult to test scenarios where transactions are sponsored by another account, requiring manual workarounds outside of the Simnet environment.
To support unit testing for sponsored transactions, I propose adding a sponsorPrivateKey parameter in the constructor of CallFnArgs. This way, when calling callPublicFn with a sponsor key, the transaction will be considered a sponsored transaction.
Currently, it is not possible to perform unit testing for sponsored transactions using Simnet in Clarinet. This limitation makes it difficult to test scenarios where transactions are sponsored by another account, requiring manual workarounds outside of the Simnet environment.
To support unit testing for sponsored transactions, I propose adding a
sponsorPrivateKey
parameter in the constructor ofCallFnArgs
. This way, when callingcallPublicFn
with a sponsor key, the transaction will be considered a sponsored transaction.Current Implementation:
Proposed Implementation:
By including this optional parameter, developers can write unit tests that simulate sponsored transactions directly in Simnet.
Alternatives solution:
The text was updated successfully, but these errors were encountered: