markdown guide

I think this project can come handy! I have never used it myself though. For me, it was always enough to write tests with mocha & chai (i.e. test that arguments are parsed correctly and your internal logic). What exactly do you want to achieve by testing via CLI?


I think you could probably write another small app if you really need to do testing right at the CLI that know what inputs and outputs to look for. A miniature "postman" for your app. I would submit that you should first make sure everything before the CLI is tested correctly. If you have internal tests for all logic/processing/CRUD in your application there is really very little to test at the CLI. What functionality or behavior are you wanting to test there that can't be tested internally?

Classic DEV Post from Apr 11

What's in your podcast rotation right now?

Curious what everyone is listening to for podcasts these days, whether it be te...

Móricz Gergő profile image
document.write(new Date().getFullYear() - 2005); year old programmer.

If crime-fighting half-man/half-sharks can do it, so can you.