Skip to content


Here are 405 public repositories matching this topic...

headsvk commented Mar 19, 2021

I took me some debugging to find out why my property tests with Koin fail.
I expected KoinListener would reset Koin after each test, no matter if it's a basic test or a property test.

Then I found out that the second run of my simple test reuses the values saved in Koin from the first run.

checkAll<Boolean> { arg -> // true/false
  declareMock {
quijote commented Oct 11, 2021


AssertJ error messages currently do not take into account that toString of asserted values may contain new lines.

The resulting error messages can at times look awkward due to missing indentation.


For example let's consider a class where toString returns multi-line XML:


For simplicity I will use the fo

xamgore commented Dec 14, 2020

Let's dive into the source code:

Only [Symbol.iterator] property is checked, meaning the value is at least Iterable<T>. It may be IterableIterator<T> if the presence of one more property, next, is ensured.

interface Iterable<T> {
    [Symbol.iterator](): Iterator<T>;
jgirault-qs commented Jul 23, 2021

Describe the bug
pa.errors.SchemaErrors.failure_cases only returns the first 10 failure_cases

  • I have checked that this issue has not already been reported.
  • I have confirmed this bug exists on the latest version of pandera. 0.6.5
  • (optional) I have confirmed this bug exists on the master branch of pandera.

Note: Please read [this guide](https://matthewrocklin.c

authorjapps commented Aug 5, 2020

I want a documentation or Wiki page where the expected vs actual field matching is explained
So that I can use these in my test automation to test the server response payloads and headers
e.g. id=123 , id="123", isValid=true, isValid="true" etc


Cover the following currently supported mechanisms with examples

  • $EQ
  • (int)
  • (float) or (decimal)
  • (boolean)
rhushikesh commented Oct 17, 2021

Platform (all, jvm, js): jvm
Extension (none, kotlin 1.3): none

Code related feature

//instead of

expect(path).feature { f(it::isExecutable) }.toEqual(false)
Following the things you need to do:


extend PathAssertions with a function isNotExecutable (see PathAssertions as a guideline)
implement isNotReadable in DefaultPathAssertions.kt by

alexjeffburke commented Dec 7, 2019

Normally, the "to be truthy" assertion does not take any value as it simply asserts that a subject can be coerced to a boolean true (in the case of "to be falsy" it is coercion to boolean false).

It seems that early on these assertions inherited an optional form where a custom message can be supplied as their argument - this was likely inspired by earlier assertions frameworks (assert on node

Improve this page

Add a description, image, and links to the assertions topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the assertions topic, visit your repo's landing page and select "manage topics."

Learn more