Thursday, January 3, 2019
I'm already familiar with the reasons to have a test coverage badge in each Rails project. While I'm sure that the test coverage measurements have limitations, I believe that it's better to have a test coverage than to not have one.
However, I've learned that an open source project that I'm working on used to have a test coverage badge but no longer does. What is the case AGAINST test coverage badges?
-- However, I've learned that an open source project that I'm working on used to have a test coverage badge but no longer does. What is the case AGAINST test coverage badges?
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/6b61f51a-030b-47a8-8121-14711d17172d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment