TrueCloudLab/neoneo-go
7
0
Fork 2
Code Issues Pull requests Projects Releases Packages Wiki Activity

neotest: improve doc based on #3120

Browse source 
We don't want anyone to have the same problem.

Signed-off-by: Roman Khimov <roman@nspcc.ru>
This commit is contained in:
Roman Khimov 2023-09-05 15:19:13 +03:00
parent 2f54f176fb
commit 4c015b30d5
1 changed files with 6 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
pkg/neotest/doc.go
View file

@ -15,5 +15,11 @@ Usually it's used like this:
Higher-order methods provided in Executor and ContractInvoker hide the details 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 of transaction creation for the most part, but there are lower-level methods as
well that can be used for specific tasks. 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 package neotest