Move _filetest.gno to filetests/* folder.

[jaekwon]

The _filetests clog the gno package directory; instead of _filetest.gno, we should move the files into a ./filetests/ folder, and remove the _filetest.gno file extension.

[moul]

@harry-hov whats the current state, did you start?

I think it could be a good task for @gfanton yo complete his onboarding on the VM + CLI parts of the project.

[gfanton]

it doesn't looks too complicated at first glance, I can try to do this, but maybe @harry-hov already have something

[gfanton]

I've initiated a small pull request #1062. It seems to work naturally by simply adding filetest files from the filetests directory to the subpkg without any extra steps.
A few quick questions that come to mind:

• Can the filetests folder contain _test.gno files or any other special files that is not a filetest, (like a gno.mod)?
• Are subdirectories allowed in this folder? If so, what happens if a filetests subdirectory is present within that folder?
• Should we support both (_filetest file and filetests directory) ?

[harry-hov]

it doesn't looks too complicated at first glance, I can try to do this, but maybe @harry-hov already have something

I started working on that with my another work about publishing subdirs.
Since we are moving the _filetest.gno files to subdir(/filetests), due to this change, they will not be published to the chain. So i waited to finish work on publishing subdirs before making this change.

I followed a similar approach to what you did in your PR #1062. I cherry-picked and pushed my commit here(harry-hov@dfe2e8b) just in case if you want to take a look

[gfanton]

@harry-hov Is this feature truly dependent on publishing subdir? Given that filetests are not executed on-chain (yet?), can we not handle this separately?

[harry-hov]

@harry-hov Is this feature truly dependent on publishing subdir?

Not exactly. I would just like to have that feature first.

But TBH. i have no preference. if your PR is ready we can go ahead with this change first (considering we are okay with not publishing filetests on chain)

[thehowl]

See-also: #1346 as an alternative. As a more radical approach, but I think better in the long term, I propose removing filetests for end users altogether :)

[moul]

I suggest doing the opposite by allowing them and adding support for txtar testing as well. Allowing this doesn't imply favoring them over standard unit tests. It aims to make it easier for users needing this feature to work outside the main monorepo. The goal is to allow creating a standalone repository with .gno files, _test.gno files, and a subfolder for advanced tests, catering to advanced users.

cc @gfanton