-
Contemplate the utility of Newton (invariants) as specifications for property based testing. I got this idea from [this paper](https://dl.acm.org/doi/10.1145/1941054.1941055).
-
I'm investigating property-based testing for Oxen projects, I think libsession-util is a good start, and `session::bt::merge` is a good toy study case.
To use property-based testing, the first step…
-
Using e.g. https://github.com/dubzzz/fast-check/
-
## Problem
Due to auto-generated nature of the client and the heavily nested query arguments, there are many possible combinations of arguments and methods that we do not have tests for.
## …
-
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 fo…
-
Currently it's possible only with additional libs that can generate sets of values.
-
Currently, it's very natural to express properties using `satisfies`, and with a fix for #1633, debugging errors that are uncovered by generated input is quite straightforward. The last typical piece …
-
Copying from #13098
"Just wondering if people have thought about property-based testing rather than example-based testing. unit_threaded allows for check in D. proptest and quickcheck are available…
-
Python is a lightweight interpreted programming language. Property-based API testing techniques in Rust (quickcheck and proptest) are prohibitively expensive. Extensive use of the [hypothesis package]…
-
**Example scenario:**
1. A function takes an argument of type `Filters`:
```kotlin
data class Filters(val olderThan: Instant?, val cheaperThan: Money?, val hasTags: Set?, ...)
```
2. We are u…