mzdun / cov Goto Github PK

Note: this is only feature-worthy.

• prepare serializer
• attach to cov report
• attach to cov log (also prepare for branch coverage in docs)
• attach to file-level cov show
• attach to cov show table
• %C(rating:fn)

• find subset of information common to gcov and llvm-cov
• investigate jest branch coverage capabilites
• create JSON schema
• create branch_coverage / "bran" SERDES
• create cov::branch_coverage interface
• update report to write "bran" when available
• update show to read "bran"
  • and show it in tables
  • and show it in file printout

The <rev>..<rev> has only sense, where there is a history, same for <rev>~ and <rev>^. Builds have none, but showing a single build is wanted, and is currently thwarted by rev parser

• disallow paired revs and ~/^ suffixes for all, but reports, but single unadorned revs should be valid, if they are visible to repo in any form
• add warning to cov log if a revison fails is_a<cov::report> test
• add cov show view for cov::build coming from an unpaired revision
• add cov show view for cov::files coming from an unpaired revision
• add warning to cov show if unpaired revison fails all is_a<cov::report>, is_a<cov::build> and is_a<cov::files> tests
  • only cov::object_with_id can be located and only those classes implement it.

There is need to locate filters in more, than one directory -- and it should not be $PATH.

• Prepare platform::run_filter (and possibly platform::run_tool) to accept environment variable to look for their respective programs
  • Posix (with : as path separator)
  • Windows (with ; as separator)
• Use current root directory as fallback

Note: this is only fix-worthy.

Note: this is only fix-worthy.

• parse loops ops: %L(build){ … %}
• introduce formatter sub-views façades
• change --decorate to mean "with labels"
• add --[no]-prop-names to cov show and cov log (defaulting to no)
• update format_descriptions in show_range.cc:
  • short & medium
  • full & fuller
  • raw

full, fuller

- build $BUILD
  Config:   %mD
  Coverage: [%pP] %C(faint normal)%pC/%pR%Creset %C(faint rating)(%pr)%Creset

raw

- build $BUILD
  files $FILE_LIST
  stats $RAW_STATS
  props $JSON_DICT

• make sure peel_target ends
• make sure tools::resolve ends

• remove a build by reference from top report
• append a build by report JSON + propset, error if propset already in report?
• update a build by report JSON + propset?
• cov show changes: take a list of properties to select only some builds

• add message for any missing cov::errc
• consider message for any missing git::errc
• freeze the language identifiers

• If --force == stability,
  • if stability is empty, perform normal version bump and set stability to "-rc.1"
  • otherwise, bump stability counter (or set to ".2", if missing)
• otherwise,
  • if stability starts with "-rc.", drop stability
  • otherwise, perform normal version bump

at least on Linuxes, pipe the output throught less

• add --pipe to main app
• investigate pseudo terminal on linux
• patch all uses of is_terminal, if pty is not possible
• investigate pty-analogue on Windows
• provide more as alternative on Windows

For given reference, produce a view of the coverage

• new command (including translations)
• add optional propset to the JSON schema
• add additional JSON schema for collection of reports -- textual inclusion or external reference
• support --json
• support --html

Currently, only functions with the same demangled names are aliased for the console printout. But, while different destructors will have the same demangled name, different instantiations will differ.

• Alias by position alone — all functions occupying the same space are the same function
• Alias also during stats calculations — if we are treating the functions as called in printout, store "better" stats
• Decide the color cues based on whole alias, but still show 0x for uncalled function, where neither name nor demangled name matches.