Generate json output from cover

[glyphrider]

In an effort to incorporate output from cover into our automated build (CI) process, I created the ability to export the coverage information to a JSON file. This is done per-module, to simplify cross-application aggregation. added a new option

{cover_export_json,true}.

which should be using in conjunction with {cover_enabled,true}. to produce output file(s) of the form module_name.COVER.json in the .eunit directory.

A retest suite is provided to illustrate the generation of the file(s).

[ghost]

Shouldn't this use retest_log instead?

[glyphrider]

Yes. Actually, it probably should have been cleaned up (removed before pushing). The learning curve on retest was a little sharp; I never found any good documentation, so most of this is stolen from the eunit retest.

[ghost]

Dave built retest for rebar integration tests, and there is no documentation besides the tests, but for whats it's worth it's very simple.

[ghost]

Thanks, in addition to the 0fea93c inline comments, please:

• get rid of the merge commit (see pull-requests-and-branching)
• rewrite the commit message following writing-commit-messages
• for consistency, a comma (if not in a string) should be followed by a space
• add a copyright header in cover_rt.erl
• append your name in THANKS

[glyphrider]

Addressed inline comments, adjusted commit message, improved comma consistency added copyright header, appended name to THANKS, then rebased.

[ghost]

Don't you mean Brian H. Ward?

[ghost]

missing space after comma

[ghost]

@ferd?

[ferd]

Yes?

[ghost]

Any thought on this?

[ferd]

I have no way to test this, have no use for the feature personally, but if the code looks clean and it helps people, I see no reason not to introduce it apart from me not knowing what is 'expected correct behaviour' from this item.

[ghost]

I don't know if there already exists a prior implementation in some cover utils package that might differ in output, but it's simple and seems to be useful for integration in systems that don't have an Erlang term reader.