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
It is quite inconvenient to always have to specify gno test -v . when trying to run tests in a directory with the help message asking to specify a directory
Suggestion
Make it similar to the go test command that'll try to run within the current working directory if the package names aren't specified
)
This PR resolves#3420 by enhancing
the gno test command.
The command now assumes the current directory (.) as the default path
when no directory is specified, aligning its behavior with go test.
Changes to CI:
- Removed the no_args test.
- Added new tests to cover the following scenarios:
- Valid test execution.
- Valid file-based test.
- Test with flags.
- Empty directory.
- Empty test file.
This PR is a repost of #3429 with a
cleaner commit history.
CC @notJoon@moul
---------
Co-authored-by: Nemanya21 <[email protected]>
Co-authored-by: Leon Hudak <[email protected]>
Description
It is quite inconvenient to always have to specify
gno test -v .
when trying to run tests in a directory with the help message asking to specify a directorySuggestion
Make it similar to the
go test
command that'll try to run within the current working directory if the package names aren't specifiedThis is an issue request @petar-dambovaliev @moul
The text was updated successfully, but these errors were encountered: