test: new txtar test for non-regression

[moul]

I don't think we need to merge this pull request, but I wanted to open it to check a few points:

• We have three main folders containing txtar files. Is there a current contributing guideline explaining when to use one folder over another?
• Is this test currently only testable using txtar, or is there a better approach?

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 54.71%. Comparing base (3b42391) to head (88ebb51).
Report is 259 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #2343   +/-   ##
=======================================
  Coverage   54.71%   54.71%           
=======================================
  Files         590      590           
  Lines       79036    79023   -13     
=======================================
- Hits        43243    43237    -6     
+ Misses      32543    32536    -7     
  Partials     3250     3250           

Flag	Coverage Δ
contribs/gnodev	23.81% <ø> (ø)
contribs/gnofaucet	14.46% <ø> (-0.86%)	⬇️
contribs/gnokeykc	0.00% <ø> (ø)
contribs/gnomd	0.00% <ø> (ø)
gno.land	62.68% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[deelawn]

We have this issue as well to do part of this #2253

[thehowl]

The way this can be done in filetests, is by adding the aaa packages in gnovm/tests/extern (which is a directory of imports, only available in filetests); and then doing the import in a filetest.

I think it makes sense to put it there, as it's testing GnoVM behaviour with imports, not gno.land behaviour.

[github-actions]

This PR is stale because it has been open 3 months with no activity. Remove stale label or comment or this will be closed in 3 months.