Skip to content
This repository has been archived by the owner on Sep 7, 2018. It is now read-only.

default mode separate test name from test case name #254

Closed
faassen opened this issue Aug 6, 2012 · 4 comments
Closed

default mode separate test name from test case name #254

faassen opened this issue Aug 6, 2012 · 4 comments

Comments

@faassen
Copy link

faassen commented Aug 6, 2012

When a test fails on FF Linux, I get output like this identifying the test failure:

Firefox 14.0.1, Linux sync tests source update from HTTP response

This is in test case 'sync tests' and in the test 'source update from HTTP response'. But no separation between browser identification, test case identification and test identification is made.

I understand that buster.js's test reporting feature hereby advocates constructing a test case name and a test name in such a way that they form a sentence together. I'm not sure how that is supposed to work, so I think more documentation is warranted, unless I missed it.

This also seems to be an approach not common to most test runners in my experience. I expect a separation between browser, test case name and test name to be clearly visible in the output. Should buster do test naming advocacy or should at least the default mode be one where things are separated?

Firefox 14.0.1, Linux | sync tests | source update from HTTP response

@cjohansen
Copy link
Member

There are other reporters that display this differently. In the next version, browser will be separated clearly. We'll review this issue after the next version is out.

@dwittner
Copy link
Member

dwittner commented Nov 1, 2014

@cjohansen, brief reporter still doesn't separate browser. Couldn't we just change this line to

return env.contexts.concat(event.name).join(" | "); 

That way the contexts are separated visually, but can still be read as one sentence.

@cjohansen
Copy link
Member

Sure!

@dwittner
Copy link
Member

dwittner commented Nov 2, 2014

Implemented in version 0.7.10 of buster-test.

@dwittner dwittner closed this as completed Nov 2, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants