feat(test): handle empty args by assuming current directory for gno test

[Nemanya8]

This PR addresses Issue #3420 by improving the gno test command. It now assumes the current directory (.) as the default path when no directory is specified, similar to go test.

[Gno2D2]

🛠 PR Checks Summary

All Automated Checks passed. ✅

Manual Checks (for Reviewers):

• IGNORE the bot requirements for this PR (force green CI check)
• The pull request description provides enough details

Read More

🤖 This bot helps streamline PR reviews by verifying automated checks and providing guidance for contributors and reviewers.

✅ Automated Checks (for Contributors):

🟢 Maintainers must be able to edit this pull request (more info)

☑️ Contributor Actions:

1. Fix any issues flagged by automated checks.
2. Follow the Contributor Checklist to ensure your PR is ready for review.
   • Add new tests, or document why they are unnecessary.
   • Provide clear examples/screenshots, if necessary.
   • Update documentation, if required.
   • Ensure no breaking changes, or include BREAKING CHANGE notes.
   • Link related issues/PRs, where applicable.

☑️ Reviewer Actions:

1. Complete manual checks for the PR, including the guidelines and additional checks if applicable.

📚 Resources:

• Report a bug with the bot.
• View the bot’s configuration file.

Debug

Automated Checks

Maintainers must be able to edit this pull request (more info)

If

🟢 Condition met
└── 🟢 The pull request was created from a fork (head branch repo: Nemanya8/gno)

Then

🟢 Requirement satisfied
└── 🟢 Maintainer can modify this pull request

Manual Checks

**IGNORE** the bot requirements for this PR (force green CI check)

If

🟢 Condition met
└── 🟢 On every pull request

Can be checked by

• Any user with comment edit permission

The pull request description provides enough details

If

🟢 Condition met
└── 🟢 Not (🔴 Pull request author is a member of the team: core-contributors)

Can be checked by

• team core-contributors

[Nemanya8]

The test case for no arguments currently fails, which is expected due to the changes. However, if we are moving forward with this merge, the test case should be updated accordingly. Please let me know if you'd like me to handle the update.

[notJoon]

the test case should be updated accordingly. Please let me know if you'd like me to handle the update.

I confirmed that it runs well when executed locally. It seems we need to make the CI pass, so could you modify the tests if possible?

[Nemanya8]

so could you modify the tests if possible?

Could you guide me on modifying the tests? Should I only adjust the test with no arguments, or should I add a variation without path arguments for each test? The latter approach is more thorough, but it would basically double the testing time.

[moul]

need some unit or integration tests.