forked from TrueCloudLab/neoneo-go
neotest: improve doc based on #3120
We don't want anyone to have the same problem. Signed-off-by: Roman Khimov <roman@nspcc.ru>
This commit is contained in:
parent
2f54f176fb
commit
4c015b30d5
1 changed files with 6 additions and 0 deletions
|
@ -15,5 +15,11 @@ Usually it's used like this:
|
|||
Higher-order methods provided in Executor and ContractInvoker hide the details
|
||||
of transaction creation for the most part, but there are lower-level methods as
|
||||
well that can be used for specific tasks.
|
||||
|
||||
It's recommended to have a separate folder/package for tests, because having
|
||||
them in the same package with the smart contract iself can lead to unxpected
|
||||
results if smart contract has any init() functions. If that's the case they
|
||||
will be compiled into the testing binary even when using package_test and their
|
||||
execution can affect tests. See https://github.com/nspcc-dev/neo-go/issues/3120 for details.
|
||||
*/
|
||||
package neotest
|
||||
|
|
Loading…
Reference in a new issue