Closed therealbytes closed 6 days ago
@therealbytes I would love to work on this
This is how I intend to tackle this issue
I would use the new mock caller, create unit tests for each method, utilizing the generated mocks to simulate different scenarios. Define expected inputs and outputs, configuring the mocks to return these outputs for the specified inputs. Call the methods on the mock implementations and use assertions to verify that actual outputs match expected outputs. Finally, execute the tests using the Go test tool to ensure all methods function as expected.
Looking forward to working on this. Thank you
Any progress with this? @kateberryd
@therealbytes I'm waiting on #37 to kickstart
Hi @therealbytes #37 is completed and I've commenced work, will open a PR soon
Hello @therealbytes, fab here, in the last ODHack I contributed to this great project creating some unit tests, thus, I have context to work on this issue, I would love to keep contributing to it, so if this issue is available I would like to take it. :)
Rationale
Currently, the Concrete environment is poorly tested.
Implementation
This depends on #37 being implemented. Once that is done, the new mock caller can be used for testing. Both execution and gas usage should be tested.
At the moment, the caller methods are:
Note that the two create methods will be modified by #32 .