python-test-framework
python-test-framework copied to clipboard
codewars
Codewars test framework for Python
the current wording, while correct, seems to clash a bit with beginner expectations, it can easily be misread as "given input x, expected y" the (especially beginner) solver is likely...
A minor change which gracefully handles `AssertException` thrown by assertions from inside of test cases decorated with `@test.it`. The fix should allow authors to use `allow_raise = True` in a...
AssertionError doesn't show up in the output when it's raised inside a function decorated by `test.describe`, `test.it`, or inside any function called by those. It correctly stops the execution, emits...
* removed the use of `test.expect_no_error` inside the timeout utility: - done "manually", allowing to handle data passed to the thread - consequence: DOCS need an update because there isn't...
ok, there are actually several problems about it. ## Context So far, it handles properly: * error raised in the function of the user while running * wrong output from...
- Stops at first failure like most other test frameworks - Single test passed message regardless of the number of assertions - Discourage fat test cases - Allow using external...
We can't use assertions from libraries yet because of this. See https://github.com/codewars/python-test-framework/pull/5#issuecomment-645184231
I created a module forbidder some time ago and it began to "spread in the wild" already. If it's incorporated to the framework, it will be more easily maintainable. That...
Currently both JS and Python versions have test constructs to test if some pieces of code runs under a certain time limit, but they do not allow the use of...
this should be valid, and should be considered a success: ```py import codewars_test as test @test.it("") def _(): pass ``` and perhaps by extension, multiple successful assertions should only result...