cegonse/cest

Issues

• README suggests that Cest cannot be used for C projects

  #78 opened a year ago by guyikcgg
  0

• Print exception contents when test fails due to exception

  #76 opened 4 years ago by jorsanpe
  0

• Parametrized tests should be documented

  #75 opened 4 years ago by cegonse
  0

• Example tests should be runnable and modifiable in docs

  #74 opened 4 years ago by cegonse
  0

• Assert functions should have HTML documentation

  #73 opened 4 years ago by cegonse
  0

• Fix JUnit report support

  #72 opened 4 years ago by cegonse
  0

• Add Windows + Visual Studio support

  #71 opened 4 years ago by cegonse
  0

• Align verbose test results with Jest

  #70 opened 4 years ago by cegonse
  0

• Support parameterized test cases

  #63 opened 4 years ago by jorsanpe
  0

• Support asserting exceptions

  #66 opened 4 years ago by cegonse
  0

• Support randomized test suite and case execution

  #10 opened 4 years ago by cegonse
  0

• Support negation of matchers in expectations

  #9 opened 4 years ago by cegonse
  1

• Support property based test cases

  #64 opened 4 years ago by jorsanpe
  0

• Add support for custom test runners

  #62 opened 4 years ago by jorsanpe
  0

• Improve string expectation error message readability

  #56 opened 4 years ago by jamofer
  0

• Support focusing tests through fit keyword

  #5 opened 4 years ago by cegonse
  0

• Review compilation warnings with -Wsign-compare

  #57 opened 4 years ago by jamofer
  0

• Support debugging of test cases

  #49 opened 4 years ago by jorsanpe
  1

• Support skipping tests through xit keyword

  #4 opened 4 years ago by cegonse
  0

• Support regexp expectation matcher for strings

  #7 opened 4 years ago by cegonse
  0

• Support after and before all test-suite level setup and teardown

  #8 opened 4 years ago by cegonse
  0

• Tests should fail upon raising an exception signal

  #41 opened 4 years ago by cegonse
  1

• Test cases could be run as child processes

  #38 opened 5 years ago by jorsanpe
  1

• Allow configuration of Cest verbosity

  #37 opened 5 years ago by jorsanpe
  0

• Implement functions to inconditionally pass or fail tests

  #36 opened 5 years ago by jorsanpe
  0

• Expand README.md with basic information

  #19 opened 5 years ago by cegonse
  0

• Catch exceptions raised by SUT

  #33 opened 5 years ago by jorsanpe
  0

• Support comparison of lists of objects

  #30 opened 5 years ago by jorsanpe
  1

• Expects continue to be executed even if the first one fails

  #27 opened 5 years ago by jorsanpe
  0

• JUnit XML generation is not covered by tests

  #28 opened 5 years ago by cegonse
  0

• Support execution of a subset of test cases with a matcher

  #25 opened 5 years ago by cegonse
  0

• Framework tests in Python should be executed in CI pipeline

  #21 opened 5 years ago by cegonse
  0

• Using a comma inside a test case will break the describe macro

  #22 opened 5 years ago by jorsanpe
  0

• Automatically detect all tests under spec directory

  #17 opened 5 years ago by cegonse
  1

• Unicode strings are not correctly handled by JUnit results parser

  #15 opened 5 years ago by cegonse
  1

• Setup action to execute all tests upon push to master

  #6 opened 5 years ago by cegonse
  1

• Generate JUnit XML test report files

  #3 opened 5 years ago by cegonse
  1

• Return with error code in main function when some test fails

  #11 opened 5 years ago by jorsanpe
  1

• Review compilation warnings

  #2 opened 5 years ago by cegonse
  1

• Report test case line number when test passes

  #1 opened 5 years ago by cegonse
  1