Tests for command line args

[Mause]

No description provided.

[Mause]

Is it worth implementing this?
Or should we simply stick with unit tests for the underlying functions?

[milesrout]

It does make some sense to test command line arguments, but how do you test them?

[Mause]

Shell script, and diff the output?
On Dec 24, 2013 6:29 AM, "Miles Rout" [email protected] wrote:

It does make some sense to test command line arguments, but how do you
test them?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/10#issuecomment-31147736
.

[milesrout]

Some StackOverflow threads:

http://stackoverflow.com/questions/353198/best-way-to-test-command-line-tools
http://stackoverflow.com/questions/7029875/automating-integration-testing-for-a-command-line-application

Expect could work well.

[Mause]

I think what I was thinking was, i think the term is integration tests, where you test what the user will actually be interacting with

[milesrout]

i think the best way would just be to do manual testing of the UI before releases, when we have enough of the toolchain done to do releases. Until we do, the interface and output it going to change fast enough that will probably have to re-write the tests each release, and that's more work than just doing manual testing.