Tests in the validators folder with file name ending w/ .test.ak, can't be executed with aiken check -m module_name

[nemo83]

What Git revision are you using?

Currently running aiken v1.1.10+b25afa2

What operating system are you using, and which version?

• Linux / Ubuntu
• Linux / Other
• [x ] macOS
• Windows

Describe what the problem is?

I'm working on a large project https://github.com/cardano-foundation/cardano-ibc-incubator (in the cardano/onchain folder) and this projects contains several validators.

Each validator in the validators folder has a production module and a test module. An example is the spending_transfer_module which has:

• production code https://github.com/cardano-foundation/cardano-ibc-incubator/blob/fix/ID-101-less-expect-more-and/cardano/onchain/validators/spending_transfer_module.ak
• test code: https://github.com/cardano-foundation/cardano-ibc-incubator/blob/fix/ID-101-less-expect-more-and/cardano/onchain/validators/spending_transfer_module.test.ak

When I try to run in isolation the tests for the spending_transfer_module module, with any of the commands:

aiken check -m `spending_transfer_module`
aiken check -m `spending_transfer_module.test`
aiken check -m `spending_transfer_module_test`

the output is empty like it could not find the tests in the module or the test module altogether.

What should be the expected behavior?

Test contained in the validators/spending_transfer_module.test.ak module are run.

[KtorZ]

@nemo83 There's indeed an issue. What is happening is that because the -m option allows you to pass either a test name or a module name, passing only -m spending_transfer_module results in the command looking for a test named spending_transfer_module.

I'll try to come up with a fix, but for now, you can disambiguate the filter for the command by passing:

aiken check -m "spending_transfer_module.{}"

Which makes it parse as a module filter.

[KtorZ]

Okay. So, I didn't fix it in the end, but I opted for better errors and user feedback. Now, test output will come with extra Collecting steps detailing how the filtering options are being interpreted. For example:

command-line options	output
ø
-m placeholder
-m placeholder.{..}
-m "placeholder.{foo, bar}"

In addition, the case where you specify a module name interpreted as a test scenario is now detected and triggers a warning which suggests the right syntax, like so:

I believe, these additions solve the problem nicely.

[nemo83]

LGTM, thank you.