Skip to content

Releases: codewars/ttester-codewars

Relabel custom print functions

30 Oct 00:05
Compare
Choose a tag to compare

Relabel custom print functions. Improve formatted output.

Protect against accidental redefines

29 Oct 23:13
Compare
Choose a tag to compare

Some user code unintentionally redefined words causing tests to unexpectedly fail. Introduce vocabularies to protect against accidental redefines.

Robust handling of too many results in testcase

27 Oct 23:25
Compare
Choose a tag to compare

Minor release to improve handling of test cases where too many elements are either produced or expected.
Currently the Testest framework can handle 32 normal plus 32 float results.
No regular Forth words ever produce that many results, so this is a very reasonable upper bound for authors writing tests.

Robust floating point support

23 Oct 21:38
Compare
Choose a tag to compare

Robust floating point support using a completely rewritten implementation. First major release.

Extended floating point support

22 Oct 21:23
Compare
Choose a tag to compare

Release with extended floating point support, including testing for relative, absolute, and custom floating point equality.

Floating point support

21 Oct 23:00
Compare
Choose a tag to compare
Pre-release

This major rewrite of the ttester testing framework adds support for adding floating point code to your tests.
The regular stack and the floating point stack can be mixed, but will be tested strictly separately, although reporting is combined.
Passes all tests, but needs integration testing on Codewars, especially w.r.t. to the new formatted test outputs.

v0.0.4

19 Aug 16:57
eca12fe
Compare
Choose a tag to compare
  • Show the expected stack from bottom (same order as test cases) (#10, #11)

v0.0.3

09 Aug 17:06
2df3bb6
Compare
Choose a tag to compare
  • Fix dropping past the arguments stack causes test display to show wrong numbers (#6)

v0.0.2

02 Aug 23:18
ca9496f
Compare
Choose a tag to compare
  • Add s# to test strings (#4)

v0.0.1

30 Jul 18:54
0c496b3
Compare
Choose a tag to compare

Bug Fixes

  • Fixed bug caused by stack mismatch (#1)