cli: allow execute custom test command

[fanatid]

Closes #426

Usage example:

anchor test --cmd "npx ts-node node_modules/.bin/tape tests/*.ts"

[armaniferrante]

What do you think of adding this to the [scripts] section instead of the --cmd option?

So your example turns into

[scripts]
test = "npx ts-node node_modules/.bin/tape tests/*.ts"

Then run anchor test.

[fanatid]

If we add test field to scripts section which will be used by anchor test what does anchor run test should do?

[armaniferrante]

If we add test field to scripts section which will be used by anchor test what does anchor run test should do?

Perhaps the same as anchor test? I'm not sure.

I'm thinking it'll be convenient for some of the scripts to have special behavior similar to npm, for deploys, tests, and publishing builds (once that's ready).

[armaniferrante]

Shall we add a simple test in one of the examples?

[fanatid]

Yeah, I thought about example and where we should document the new feature. Maybe we should introduce breaking change and require test field in scripts section? i.e. move mocha/ts-mocha from cli binary to config and create it by default?

[armaniferrante]

Yeah, I thought about example and where we should document the new feature. Maybe we should introduce breaking change and require test field in scripts section? i.e. move mocha/ts-mocha from cli binary to config and create it by default?

I don't have strong opinions. Let's file an issue and consider the breaking change separately.

[fanatid]

Updated.

• Use command from [scripts] + test
• On anchor init add default [scripts] + test for mocha/ts-mocha
• Instead file allow to pass custom arguments