jepsen
hypothesis
Our great sponsors
jepsen | hypothesis | |
---|---|---|
3 | 20 | |
6,603 | 7,275 | |
1.2% | 1.5% | |
7.6 | 9.9 | |
about 1 month ago | 4 days ago | |
Clojure | Python | |
- | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
jepsen
-
MongoDB is actively investigating a security incident
aphyr seems to still work on it, so probably just not that many companies who want to pay to get told the truth anymore: https://github.com/jepsen-io/jepsen
-
What Is Property Based Testing?
One very nice example of this is Jepsen:
https://github.com/jepsen-io/jepsen
-
ZooKeeper-free Kafka is out. First Demo
https://github.com/jepsen-io/jepsen/issues/399
> Yeah! I mean, I find a lot of linearizability errors in various databases, but this was also my very first time doing this kind of test, and it varies from system to system. Could have easily slipped through the cracks.
In summary, aphyr thought Zookeeper is linearizable even though it doesn't provide linearizable ops.
Looks like Zookeeper needs to be tested again.
hypothesis
- Hypothesis
-
A Tale of Two Kitchens - Hypermodernizing Your Python Code Base
Hypothesis for Property-Based Testing: Hypothesis is a Python library facilitating property-based testing. It offers a distinct advantage by generating a wide array of input data based on specified properties or invariants within the code. The perks of Hypothesis include:
-
Pix2tex: Using a ViT to convert images of equations into LaTeX code
But then add tests! Tests for LaTeX equations that had never been executable as code.
https://github.com/HypothesisWorks/hypothesis :
> Hypothesis is a family of testing libraries which let you write tests parametrized by a source of examples. A Hypothesis implementation then generates simple and comprehensible examples that make your tests fail. This simplifies writing your tests and makes them more powerful at the same time, by letting software automate the boring bits and do them to a higher standard than a human would, freeing you to focus on the higher level test logic.
> This sort of testing is often called "property-based testing", and the most widely known implementation of the concept is the Haskell library QuickCheck, but Hypothesis differs significantly from QuickCheck and is designed to fit idiomatically and easily into existing styles of testing that you are used to, with absolutely no familiarity with Haskell or functional programming needed.
-
pgregory.net/rapid v1.0.0, modern Go property-based testing library
pgregory.net/rapid is a modern Go property-based testing library initially inspired by the power and convenience of Python's Hypothesis.
- Was muss man als nicht-technischer Quereinsteiger in Data Science *wirklich* können?
-
Python toolkits
Hypothesis to generate dummy data for test.
-
Best way to test GraphQL API using Python?
To create your own test cases, I recommend you use hypothesis-graphql in combination with hypothesis. hypothesis is a property-based testing library. Property-based testing is an approach to testing in which you make assertions about the result of a test given certain conditions and parameters. For example, if you have a mutation that requires a boolean parameter, you can assert that the client will receive an error if it sends a different type. hypothesis-graphql is a GraphQL testing library that knows how to use hypothesis strategies to generate query documents.
-
Fuzzcheck (a structure-aware Rust fuzzer)
The Hypothesis stateful testing code is somewhat self-contained, since it mostly builds on top of internal APIs that already existed.
-
Running C unit tests with pytest
We've had a lot of success combining that approach with property-based testing (https://github.com/HypothesisWorks/hypothesis) for the query engine at backtrace: https://engineering.backtrace.io/2020-03-11-how-hard-is-it-t... .
-
Machine Readable Specifications at Scale
Systems I've used for this include https://agda.readthedocs.io/en/v2.6.0.1/getting-started/what... https://coq.inria.fr https://www.idris-lang.org and https://isabelle.in.tum.de
An easier alternative is to try disproving the statement, by executing it on thousands of examples and seeing if any fail. That gives us less confidence than a full proof, but can still be better than traditional "there exists" tests. This is called property checking or property-based testing. Systems I've used for this include https://hypothesis.works https://hackage.haskell.org/package/QuickCheck https://scalacheck.org and https://jsverify.github.io
What are some alternatives?
jetstream - JetStream Utilities
pytest - The pytest framework makes it easy to write small tests, yet scales to support complex functional testing
java-pubsublite-kafka
Robot Framework - Generic automation framework for acceptance testing and RPA
redpanda - Redpanda is a streaming data platform for developers. Kafka API compatible. 10x faster. No ZooKeeper. No JVM!
Behave - BDD, Python style.
Apache Pulsar - Apache Pulsar - distributed pub-sub messaging system
nose2 - The successor to nose, based on unittest2
Apache Kafka - Mirror of Apache Kafka
nose - nose is nicer testing for python
kafkacat - Generic command line non-JVM Apache Kafka producer and consumer [Moved to: https://github.com/edenhill/kcat]
Schemathesis - Automate your API Testing: catch crashes, validate specs, and save time