The State of Ruby and Testing

Re:The State of Ruby and Testing by automach on Thursday June 16, 2011 @02:41PM (#2662616)

The pie charts don't really make any sense. For example, a single project can use Cucumber, Capybara, and RSpec, or none of them, or any combination. But in the article and its graphs they are presented as mutually exclusive options.

Separating the results into exclusive types (testing framework, browser integration framework, assertion macros, etc) would make a lot more sense. Or asking what tool is being used for a particular task (unit testing, integration testing, mocking/stubbing, assertion macros, etc).

[ Parent | on HN ]

Re:The State of Ruby and Testing by aslakhellesoy on Thursday June 16, 2011 @03:02PM (#2662712)

So for all projects that use a combination of tools (the vast majority of projects I would guess), the collected data is invalid. That's too bad.

[ Parent | on HN ]

Re:The State of Ruby and Testing by danneu on Thursday June 16, 2011 @04:56PM (#2663227)

It might not make numerical sense, but it still communicates its intention.

[ Parent | on HN ]