feat: add 'gnodev test' command

[moul]

Usage

gnodev test --help    
# testOptions options
- verbose (bool) - verbose 
- root-dir (string) - github.com/gnolang/gno clone dir 

Example

gnodev test ./examples
?       ./examples/gno.land/p/avl       [no test files]
?       ./examples/gno.land/p/bank      [no test files]
?       ./examples/gno.land/p/dom       [no test files]
?       ./examples/gno.land/p/grc/grc20         [no test files]
?       ./examples/gno.land/p/grc/grc20/impl    [no test files]
?       ./examples/gno.land/p/grc/grc721        [no test files]
?       ./examples/gno.land/p/groups    [no test files]
?       ./examples/gno.land/p/maths     [no test files]
ok      ./examples/gno.land/p/rand      51.707949ms
?       ./examples/gno.land/p/releases  [no test files]
?       ./examples/gno.land/p/tests     [no test files]
?       ./examples/gno.land/p/testutils         [no test files]
?       ./examples/gno.land/p/ufmt      [no test files]
?       ./examples/gno.land/r/banktest  [no test files]
?       ./examples/gno.land/r/boards    [no test files]
ok      ./examples/gno.land/r/foo20     497.964559ms
?       ./examples/gno.land/r/nft       [no test files]
ok      ./examples/gno.land/r/releases-example  55.550871ms
?       ./examples/gno.land/r/tests     [no test files]
?       ./examples/gno.land/r/tests_foo         [no test files]
?       ./examples/gno.land/r/users     [no test files]

[moul]

[moul]

And with verbose

[moul]

@jaekwon this first version is ready for review, it requires having all the source files in a cloned gnolang/gno repo

I plan to make something like go mod download or even go mod vendor that will fetch from the chain the current published contracts that are imported by the contract in development.

But that’ll be huge, and in another PR :)

Also, I only integrated the current test mode that runs a whole file and writes the Output and Error as comment; I will then look how to manage the standard testing.T mode.

[moul]

Oops, sorry for the noise; I’ve some tests to fix (Fixed)

[moul]

new feature ides for gnodev

[anarcher]

IMHO, I feel that testing with Output and Error as comment is Gno internal testing style. (like Go's internal testscript?[1])
I think it is enough for gnodev test to support only the standard testing.T mode.

[1]: testscript was originally created for testing the Go compiler itself.

[moul]

IMHO, I feel that testing with Output and Error as comment is Gno internal testing style. (like Go's internal testscript?[1]) I think it is enough for gnodev test to support only the standard testing.T mode.

[1]: testscript was originally created for testing the Go compiler itself.

Yep I agree and I’m for going more and more with the standard go testing package as soon as it will be supported with gnodev.

Additionally to being the historical custom mode for Gno; there are still some advantages that could eventually be interesting to keep, like the format itself which is relatively like a « main » program and gives a whole new sense to contract testing (IMHO); but I hope that I will be able to mimic this with the official « func ExampleXXX » of std go which offers similar concise tests, but only supports Output and not Error.

The biggest game changer that will help get less/rid of historical testing in gno dev will certainly be a strong « testutil » package to replace everything managed with custom comments today.

Looking forward for the future Gno :)