Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

List successful tests #6

Open
phidias opened this issue Jun 9, 2016 · 3 comments
Open

List successful tests #6

phidias opened this issue Jun 9, 2016 · 3 comments

Comments

@phidias
Copy link

phidias commented Jun 9, 2016

Hi,

I started using chaplain and I like it very much. It was very easy to get started. What I found that I'm missing now is a list of the successful tests. Here is an example below (this is sbt scala tests).

chaplain-success-example

Basically, the successful tests allow you to verify that you covered all the cases (urls in this case). Also it gives you the satisfaction looking at the green colors covering your console .. hehe.

Is there any chance you can do something like that? It can be optional with a -v if you don't like it so much.

@krajzeg
Copy link
Owner

krajzeg commented Jun 9, 2016

This actually was how chaplain worked at first, but I quickly found it cumbersome with a larger number of tests . But I've also used mocha with the spec reporter and 200+ tests in the past, which looks mostly like your screenshot and scrolls past too quickly to read, so it's mostly a question of taste and what you're used to :).

Let's just say this is not a high priority - most of the work until 0.4.0 will be focused on getting the test themselves as generic and easy as possible. I hope this is not a deal breaker for you.

I'll keep this issue open and deal with it some time before 0.5.0, most probably by a "reporter" system like Mocha's.

@phidias
Copy link
Author

phidias commented Jun 9, 2016

Yeah sure. It's not a big thing this one. I can do my verification by going though the configuration file. But will be good to have one day.

Indeed, when you run all the tests it's too much to output, but when you run a smaller part of it (was just going to create a new issue about it) .. let's say a controller, then the output will be smaller and very helpful (to see if you covered everything).

@phidias
Copy link
Author

phidias commented Jun 9, 2016

Not creating a new issue .. found how you can run all the tests of a certain suite (chaplain run drinks.*)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants