[Ecosystem > Blueprint > Testing > Styleguide] #166
Description
- no
let - single expect per test
- setup() function
- component objects
- do not assume gas fees are constant
- do not depend on state generated by previous tests
- avoid 1 nanoton storage fee due to passage of time
- ...
Which topics should go here?
- preventing flaky tests: test sometimes fails for no obvious reason
- preventing slow tests: running tests takes too long
- preventing false positives: tests pass, but the code is still wrong
- preventing test code size blowup: too much tests
- preventing time loss due to unclear reason of failure: test failed, but it takes an hour to figure out why
Any kind of real-world smart-contract testing experience is appreciated here. @tact-lang/smart-contracts