Hi!
I don't know whether Bash developers are using code coverage analysis for
their QA efforts. If not, you might be interested in taking a look at the
report we created using our company's tool:
http://www.opencoverage.net/bash/index_html/sources.html
The total of 38.5% isn't that bad cons
> The total of 38.5% isn't that bad considering the condition/decision
> coverage metric. Better than other projects we tried at least.
Thanks for this.
Although it's kind of useless without knowing the context of how these graphs
were generated. How did you measure coverage? What tests did you r
> > [19:24] < dualbus> for every fix that Chet does, he introduces like 2 bugs.
> > Nice way of keeping himself busy
>
> That points to the importance of having a good, comprehensive test suite.
> It's difficult to test the interaction between features otherwise.
I apologize for my comment :-) I
