Skip to content

making the mocked prompt question and answers visible#423

Closed
pwmckenna wants to merge 1 commit intoyeoman:masterfrom
pwmckenna:master
Closed

making the mocked prompt question and answers visible#423
pwmckenna wants to merge 1 commit intoyeoman:masterfrom
pwmckenna:master

Conversation

@pwmckenna
Copy link
Copy Markdown
Contributor

No description provided.

@coveralls
Copy link
Copy Markdown

Coverage Status

Coverage remained the same when pulling 0c9f860 on pwmckenna:master into 149a1d0 on yeoman:master.

@SBoudrias
Copy link
Copy Markdown
Member

May I ask why? IMO, I hate to see Yeoman STDout output when I'm testing - there's too much already.

@pwmckenna
Copy link
Copy Markdown
Contributor Author

It was frustrating to me that I couldn't see exactly what the user will see, without manually testing. I agree that in a lot of cases, there's too much flying by, but I'd rather show everything as the user would see it, or nothing. Perhaps a seperate output toggle?

@SBoudrias
Copy link
Copy Markdown
Member

Well, your unit test are there to test functionality, not visual output - this is the task of integration tests.

Nonetheless, as you're mocking the prompt, there's no guarantee the output will be the same. As so, this is not a solution to your issue.

If you wish to test the visual, try to find a command line integration testing tool. Unit test aren't suitable for this use case.

@SBoudrias SBoudrias closed this Dec 9, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants