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

Useful formatter #19

Open
andreareginato opened this Issue Oct 3, 2012 · 10 comments

Comments

Projects
None yet
7 participants
@andreareginato
Collaborator

andreareginato commented Oct 3, 2012

Write your thoughts about the "useful formatter" best practice.

@tilsammans

This comment has been minimized.

Show comment
Hide comment
@tilsammans

tilsammans Oct 3, 2012

Great tip, Fuubar is really nice!

tilsammans commented Oct 3, 2012

Great tip, Fuubar is really nice!

@Spaceghost

This comment has been minimized.

Show comment
Hide comment
@Spaceghost

Spaceghost Oct 3, 2012

Bad practice putting it in your Guardfile instead of .rspec

Spaceghost commented Oct 3, 2012

Bad practice putting it in your Guardfile instead of .rspec

@iain

This comment has been minimized.

Show comment
Hide comment
@iain

iain Oct 5, 2012

I recently fell in love with Fivemat

iain commented Oct 5, 2012

I recently fell in love with Fivemat

@andreareginato

This comment has been minimized.

Show comment
Hide comment
@andreareginato

andreareginato Oct 6, 2012

Collaborator

Fivemat is nice, but fuubar is an alternative I would suggest more.

Collaborator

andreareginato commented Oct 6, 2012

Fivemat is nice, but fuubar is an alternative I would suggest more.

@Spaceghost

This comment has been minimized.

Show comment
Hide comment
@Spaceghost

Spaceghost Oct 6, 2012

I've used both and after the suite gets large enough, I want to use fuubar. But I like fivemat considerably. The way it shows the filename and the dots correspond to the tests/specs in the file is rather nice.

When I'm writing my tests though, I honestly prefer a documentation-like formatter.

Spaceghost commented Oct 6, 2012

I've used both and after the suite gets large enough, I want to use fuubar. But I like fivemat considerably. The way it shows the filename and the dots correspond to the tests/specs in the file is rather nice.

When I'm writing my tests though, I honestly prefer a documentation-like formatter.

@andreareginato

This comment has been minimized.

Show comment
Hide comment
@andreareginato

andreareginato Mar 9, 2013

Collaborator

I've moved the rspec configuration into .rspec as suggested by @Spaceghost

Any correction and comment to the updated guideline is appreciated.

Collaborator

andreareginato commented Mar 9, 2013

I've moved the rspec configuration into .rspec as suggested by @Spaceghost

Any correction and comment to the updated guideline is appreciated.

@fantgeass

This comment has been minimized.

Show comment
Hide comment
@fantgeass

fantgeass Aug 21, 2013

I have this string in my spec:

expect(subject.valid?(provider, link)).to be_true

When I have error, in console ouput I see this:

 Failure/Error: expect(subject.valid?(provider, link)).to be_true
       expected: true value
       got: false

The main problem is the function arguments. I see the names(provider, link), but don't see the values under that names. None of the formatters(I have tested some) show me values.

Is it possible to get that information from formatter?

fantgeass commented Aug 21, 2013

I have this string in my spec:

expect(subject.valid?(provider, link)).to be_true

When I have error, in console ouput I see this:

 Failure/Error: expect(subject.valid?(provider, link)).to be_true
       expected: true value
       got: false

The main problem is the function arguments. I see the names(provider, link), but don't see the values under that names. None of the formatters(I have tested some) show me values.

Is it possible to get that information from formatter?

@michaelmior

This comment has been minimized.

Show comment
Hide comment
@michaelmior

michaelmior Mar 19, 2014

I also prefer the documentation formatter. I think it's cool for people new to a project to easily see what the behaviour of each object. That's also why I mostly don't like #2.

michaelmior commented Mar 19, 2014

I also prefer the documentation formatter. I think it's cool for people new to a project to easily see what the behaviour of each object. That's also why I mostly don't like #2.

@Spaceghost

This comment has been minimized.

Show comment
Hide comment
@Spaceghost

Spaceghost Mar 20, 2014

@fantgeass You might want to look into the article that @dchelimsky wrote on Explicit use of subject

Spaceghost commented Mar 20, 2014

@fantgeass You might want to look into the article that @dchelimsky wrote on Explicit use of subject

@Atalanta

This comment has been minimized.

Show comment
Hide comment
@Atalanta

Atalanta Sep 21, 2014

The Fuubar formatter uses the deprecated formatter interface not supported directly by RSpec 3. (sadpanda)

Atalanta commented Sep 21, 2014

The Fuubar formatter uses the deprecated formatter interface not supported directly by RSpec 3. (sadpanda)

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