Remove test command

[ascjones]

Users can use cargo test directly for a better experience.

[HCastano]

@ascjones

While I generally agree that using cargo directly is nicer, I don't think we should've remove this so hastily.

This leaves a gap in the user experience since we already have check and build which mirror cargo. It would be natural for a user to expect that cargo contract test also exists.

As a compromise we can have cargo contract test basically just shell to cargo test under the hood.

[ascjones]

As a compromise we can have cargo contract test basically just shell to cargo test under the hood.

It looks like this is what it was already doing? https://github.com/paritytech/cargo-contract/pull/958/files#diff-f3d6c1267b6d1d54ab15b4fd1870f1802cbb73352881a1652966f7239fe674f0L85

Anyway for whatever reason it was not always working correctly, I wouldn't be averse to having it return if it did work consistently.

This leaves a gap in the user experience since we already have check and build which mirror cargo

Indeed that is a reasonable argument to have it. The counter would be that build and check are doing extra stuff on top of just passing through to cargo, and we don't mirror every cargo subcommand. Although these are the most common.

[HCastano]

Anyway for whatever reason it was not always working correctly, I wouldn't be averse to having it return if it did work consistently.

That's why I assumed it was doing other stuff, because there were issues with it, haha

and we don't mirror every cargo subcommand. Although these are the most common.

Yep, but the lack of it definitely feels awkward to me, and I'm sure users will feel the same way