Run thousands of randomly generated test scenarios based on your API specification and always be sure your API works as expected. (by schemathesis)

Schemathesis Alternatives

Similar projects and alternatives to Schemathesis

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better Schemathesis alternative or higher similarity.

Schemathesis reviews and mentions

Posts with mentions or reviews of Schemathesis. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-10-25.
  • Faster time-to-market with API-first
    12 projects | | 25 Oct 2022
    Consolidating the API specification with OpenAPI was a turning point for the project. From that moment we were able to run mock servers to build and test the UI before integrating with the backend, and we were able to validate the backend implementation against the specification. We used prism to run mock servers, and Dredd to validate the server implementation (these days I’d rather use schemathesis).
  • Show HN: Step CI – API Testing and Monitoring Made Simple
    11 projects | | 10 Oct 2022
  • API-first development maturity framework
    3 projects | | 6 Sep 2022
    In this approach, you produce an API specification first, then you build the API against the specification, and then you validate your implementation against the specification using automated API testing tools. This is the most reliable approach for building API servers, since it’s the only one that holds the server accountable and validates the implementation against the source of truth. Unfortunately, this approach isn’t as common as it should be. One of the reasons why it isn’t so common is because it requires you to produce the API specification first, which, as we saw earlier, puts off many developers who don’t know how to work with OpenAPI. However, like I said before, generating OpenAPI specifications doesn’t need to be painful since you can use tools for that. In this approach, you use automated API testing tools to validate your implementation. Tools like Dredd and schemathesis. These tools work by parsing your API specification and automatically generating tests that ensure your implementation complies with the specification. They look at every aspect of your API implementation, including use of headers, status codes, compliance with schemas, and so on. The most advanced of these tools at the moment is schemathesis, which I highly encourage you to check out.
  • This Week in Python
    4 projects | | 12 Aug 2022
    schemathesis – Run generated test scenarios based on your OpenAPI specification
  • Best way to test GraphQL API using Python?
    4 projects | | 28 Jun 2022
    Hi u/autumn_nite Python has an excellent ecosystem for GraphQL testing. Your first stop for painless GraphQL testing is schemathesis. To test your API with schemathesis, you simply need to start up your GraphQL server, and then run schemathesis like this:
  • Generating arbitrary queries for a GraphQL schema
    2 projects | | 2 May 2022
    P.S. There is a higher-level tool that wraps this library (so, one doesn't have to write Python code)
  • What advice you could give to BEGINNER?
    5 projects | | 27 Jan 2022
    It's missing the greatest API testing classic Dredd! Other than that the best API testing tool I've used so far is schemathesis. It works by looking at your API specification and automatically launching hundreds of tests per endpoint. It also leverages advanced OpenAPI documentation strategies such as links to test the relationship between various endpoints.
  • Dealing with backend developers
    5 projects | | 21 Jan 2022
    Besides other things, it provides a great data source for automatic testing. For example, Schemathesis can use it to automatically generate thousands of property-based tests (including positive & negative cases).
    5 projects | | 21 Jan 2022
    One more tip for the backend developers: make sure the API implementation is tested against the API specification using contract-testing tools such as Dredd or Schemathesis. I specially recommend schemathesis as it's a lot more comprehensive. I recommend you run those tests in the CI and require them to pass before they can merge their API changes. This is the only reliable way to ensure the API works as expected.
  • what are the best tools for documenting apis?
    6 projects | | 21 Jan 2022
    The other thing you want to make sure is that the server is implementing the API correctly. In this space, you can use tools such as Dredd and schemathesis, which look at the API specification and automatically test the server implementation against it.
  • A note from our sponsor - InfluxDB | 3 Feb 2023
    InfluxDB is the Time Series Platform where developers build real-time applications for analytics, IoT and cloud-native services. Easy to start, it is available in the cloud or on-premises. Learn more →


Basic Schemathesis repo stats
2 days ago
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives