propensive/probably

Issues

• Use Quantitative for safer table entries

  #59 opened 2 years ago by propensive
  0

• Documentation is out of date

  #73 opened 10 months ago by propensive
  0

• Provide difference when comparing mismatched numeric values in failing tests

  #68 opened 10 months ago by propensive
  0

• Fatal errors (e.g. `Mistake`) are not shown in final report

  #71 opened 10 months ago by propensive
  0

• Print a message if no tests are run

  #72 opened a year ago by propensive
  0

• Take a lock when executing benchmarks

  #70 opened a year ago by propensive
  0

• Use Turbulence IO

  #57 opened 2 years ago by propensive
  0

• Reimplement `assert` macro

  #41 opened 2 years ago by propensive
  0

• Create a static type test method

  #49 opened 2 years ago by propensive
  0

• Overhaul code to fix design issues

  #51 opened 2 years ago by propensive
  0

• Tests appear in a confusing order

  #52 opened 2 years ago by propensive
  0

• Fork comparison code into a separate project

  #53 opened 2 years ago by propensive
  0

• Include coverage data in test report

  #55 opened 2 years ago by propensive
  0

• tab-completion for command-line operation

  #34 opened 4 years ago by propensive
  0

• Show time units in output

  #29 opened 2 years ago by propensive
  1

• Provide more command-line options

  #30 opened 4 years ago by propensive
  0

• Provide coverage highlighting on request

  #63 opened 2 years ago by propensive
  0

• Handle case where coverage file does not exist

  #62 opened 2 years ago by propensive
  0

• Fix deprecation warnings

  #64 opened 2 years ago by propensive
  0

• Group non-`DefDef` nodes in their `DefDef` parent

  #65 opened 2 years ago by propensive
  0

• Implement simple tolerance allowance for comparing doubles

  #66 opened a year ago by propensive
  0

• Use Harlequin to syntax-highlight code fragments

  #67 opened a year ago by propensive
  0

• Incorporate benchmarking options where possible

  #50 opened 2 years ago by propensive
  0

• Produce HTML test reports

  #54 opened 2 years ago by propensive
  0

• Use coverage for "bug hunting"

  #56 opened 2 years ago by propensive
  0

• Avoid using deprecated `mutable.ListMap` in reports

  #60 opened 2 years ago by propensive
  0

• Code coverage output is too "flat"

  #69 opened a year ago by propensive
  0

• Make test/suite titles generic `TextType`s

  #61 opened a year ago by propensive
  0

• Confidence intervals are not calculated correctly

  #58 opened 2 years ago by propensive
  0

• `found` value spuriously displays the `Report` case class as a string

  #43 opened 2 years ago by propensive
  1

• Make `check` work like `assert`

  #40 opened 2 years ago by propensive
  0

• Add CLI tests

  #16 opened 3 years ago by propensive
  0

• work on the sbt test runner

  #31 opened 3 years ago by propensive
  0

• Explain Probably's motivation

  #27 opened 3 years ago by propensive
  0

• Scala 3 Compatibility

  #22 opened 3 years ago by ceilican
  2

• Migrate to Scala 3

  #33 opened 3 years ago by propensive
  0

• Make assertion predicates optional and repeated arguments

  #32 opened 4 years ago by propensive
  1

• provide "compiler" test runner

  #24 opened 4 years ago by propensive
  0

• Singleton `test` Runner apparently doesn't exist

  #20 opened 4 years ago by ceilican
  3

• Scala version needs to be updated from 2.12 to 2.13.3

  #21 opened 4 years ago by ceilican
  0

• Exceptions thrown by the tests are hidden

  #9 opened 5 years ago by odisseus
  1

• The Fury build definition cannot be resolved

  #11 opened 5 years ago by odisseus
  1

• Is the Maven artifact actually published?

  #14 opened 5 years ago by odisseus
  2

• Remove make capability from the Fury branch

  #8 opened 5 years ago by odisseus
  0

• `base3` terminal color is not properly reset after printing test summary

  #4 opened 5 years ago by PawelLipski
  1

• The README is a lie

  #1 opened 7 years ago by dwijnand
  1