> On May 22, 2017, at 8:47 AM, Alceu Rodrigues de Freitas Junior via > cpan-testers-discuss <cpan-testers-discuss@perl.org> wrote: > >> Maybe the most interesting thing here to see is the duplication of data in >> the report files. For example, the test state (pass, fail etc.) is expressed >> in three fields. Probably the json files could be made smaller if there was >> some normalization... > > I agree, it seems that there are some duplications that could be removed, but > without a standard established it is difficult to change anything. > > The only thing I did change is the "success" and "valid" members, that are > clearly boolean but are not using the correct JSON values. I used JSON::true > and JSON::false to replace for the correct values, but that's all.
This is the old test report format. The long-term goal (I assume) was that the LegacyReport would go away and leave only structured elements like TestSummary (see the "type" fields in the "content" field). There's now a new test report format that does not have this issue: https://github.com/cpan-testers/cpantesters-api/issues/5 <https://github.com/cpan-testers/cpantesters-api/issues/5> Joel and I are working on making this the internal format, and Garu is working on making it the format the reporters use.
