Fancier report printing

[Seelengrab]

Printing the results of a SuppositionReport is currently pretty ugly and relies on Logging:

Supposition.jl/src/testset.jl

Lines 260 to 284 in 5082b3f

	function print_results(sr::SuppositionReport, p::Pass)
	if isnothing(p.best)
	@info "Property passed!" Description=sr.description
	else
	best = @something(p.best)
	score = @something(p.score)
	@info "Property passed!" Description=sr.description Best=best Score=score
	end
	end
	function print_results(sr::SuppositionReport, e::Error)
	@error "Property errored!" Description=sr.description Example=e.example exception=(e.exception, e.trace)
	end
	function print_results(sr::SuppositionReport, f::Fail)
	if isnothing(f.score)
	@error "Property doesn't hold!" Description=sr.description Example=f.example
	else
	@error "Property doesn't hold!" Description=sr.description Example=f.example Score=f.score
	end
	end
	function print_fix_broken(sr::SuppositionReport)
	@warn "Property was marked as broken, but holds now! Mark as non-broken!" Description=sr.description
	end

It would be great to implement fancier printing here using StyledStrings.jl once it becomes available/registered.

The printing should:

• On a Pass
  • Show which property passed
  • Show the best score any example achieved, if available
  • If broken=true, ensure that this is communicated as a failure (which it's also reported as to the parent AbstractTestSet)
• On a Fail
  • Clearly communicate when a property didn't hold
  • Clearly show the minimal found inputs that made the property fail
  • If broken=true, this should be reported as known-broken, not passing or failing
• On a Error
  • Show the entire error that occurred
  • Show the stacktrace from the point of the property, up to the point where the error was thrown
  • Show the minimal example that lead to the error
  • Show how many distinct errors (if any) were encountered
  • If broken=true, this should be reported as known-broken, not passing or erroring