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
Do we have any ETA for docs on the new testing approach? 👇
There are two flavors of integration tests:
Black-box tests: execution imitates the blockchain, no access to private contract functions;
White-box tests: the test has access to the inner workings of the contract.
It isn't easy to learn the topic.
At least from the Testing overview section.
And I believe the Rust Testing Framework (in a different section) is outdated.
Topics to add:
What I can and can't test with whitebox/blackbox, very simple examples,
Which SC methods exactly can I access in both cases, and which not? For example, how to test the self.send().esdt_local_burn() triggered through the endpoint. What initial setup is required, what roles, how to set them, etc?
Simple initialization for both (whitebox/blackbox) - file structure, best practices, examples
The docs could be added systematically, not necessarily all at once, to split the work and gather feedback.
The text was updated successfully, but these errors were encountered:
Hi!
I'm terribly sorry for the inconvenience.
The trouble is, we are in a process of redesigning a lot of the testing framework, syntax-wise. Some of the documentation we might write today would become obsolete in about a month or so.
I will try though to get some of my colleagues to write on the subjects that are not subject to change in the near future.
Do we have any ETA for docs on the new testing approach? 👇
It isn't easy to learn the topic.
At least from the Testing overview section.
And I believe the Rust Testing Framework (in a different section) is outdated.
Topics to add:
The docs could be added systematically, not necessarily all at once, to split the work and gather feedback.
The text was updated successfully, but these errors were encountered: