faker
Schemathesis
faker | Schemathesis | |
---|---|---|
9 | 23 | |
17,246 | 2,147 | |
- | 2.6% | |
9.5 | 9.7 | |
6 days ago | 3 days ago | |
Python | Python | |
MIT License | MIT License |
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.
faker
-
Leveling up your custom fake data with Faker.js
Faker was originally written in Perl and is also available as a library for Ruby, Java, and Python.
-
The Uncreative Software Engineer's Compendium to Testing
Faker: a library that generates fake data that can be useful when you need data to test for various components.
-
Exploring LLMs for Data Synthesizing & Anonymization: looking for Insights on Current & Future Solutions
Don't get me wrong, LLMs are awesome but totally unsuited for what you are describing. Classic data science tools like faker will be better for the task in pretty much every aspect. They can generate synthetic datasets and anonymize existing ones faster and far more reliable than any LLM.
-
Undercover work
The Python package, Faker, is just what you're looking for!
-
Is there a way to automate testing in python? In my case :
for datatypes like string/date and other stuff, there is a Python library called faker, which you can use. It can generate fake names, fake phone numbers, dates, and addresses. here is the link to the documentation. https://faker.readthedocs.io/ here is a link to a blog post explaining Faker. https://levelup.gitconnected.com/pythons-faker-library-your-go-to-solution-for-test-data-generation-3a070065cc04
-
Testing files in Python like a pro
Then test cases became more complex. Primary data sources were often files. We needed to test pipelines. Faker still helped a lot, but it was not convenient to copy your last-best-approach for files and reinvent the wheel over and over with each project.
-
Database automation challenges and how to solve them
For a cloud-based solution, one can write their own Terraform or CloudFormation for installation as soon as their RDS instance boots up with appropriate security and authentication details. For a local dev environment, one can rely on Faker to create mock database data for your database.
-
How to create a 1M record table with a single query
Creating realistic fake data is useful in lower environments and for load testing. Outside of SQL I like faker: https://github.com/joke2k/faker
-
DuckDB: an embedded DB for data wrangling
To test a database, first you need some data. So I created a python script and used Faker to create the following CSV files:
Schemathesis
-
Ask HN: Any Good Fuzzer for gRPC?
I am not aware of any tools like that, but eventually, I plan to add support for gRPC fuzzing to Schemathesis. There were already some discussions and it is more or less clear how to move forward. See https://github.com/schemathesis/schemathesis/discussions/190...
-
Show HN: Auto-generate load tests/synthetic test data from OpenAPI spec/HAR file
Why is AI needed for this at all? Have you heard about Schemathesis (https://github.com/schemathesis/schemathesis)?
-
A Tale of Two Kitchens - Hypermodernizing Your Python Code Base
SchemaThesis is a powerful tool, especially when working with web APIs, and here's how it can enhance your testing capabilities:
- Hurl 4.0.0
-
OpenAPI v4 Proposal
I'm sorry, but you have completely misunderstood the purpose of Open API.
It is not a specification to define your business logic classes and objects -- either client or server side. Its goal is to define the interface of an API, and to provide a single source of truth that requests and responses can be validated against. It contains everything you need to know to make requests to an API; code generation is nice to have (and I use it myself, but mainly on the server side, for routing and validation), but not something required or expected from OpenAPI
For what it's worth, my personal preferred workflow to build an API is as follows:
1. Build the OpenAPI spec first. A smaller spec could easily be done by hand, but I prefer using a design tool like Stoplight [0]; it has the best Web-based OpenAPI (and JSON Schema) editor I have encountered, and integrates with git nearly flawlessly.
2. Use an automated tool to generate the API code implementation. Again, a static generation tool such as datamodel-code-generator [1] (which generates Pydantic models) would suffice, but for Python I prefer the dynamic request routing and validation provided by pyapi-server [2].
3. Finally, I use automated testing tools such as schemathesis [3] to test the implementation against the specification.
[0] https://stoplight.io/
[1] https://koxudaxi.github.io/datamodel-code-generator/
[2] https://pyapi-server.readthedocs.io
[3] https://schemathesis.readthedocs.io
-
Faster time-to-market with API-first
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
-
API-first development maturity framework
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.
-
How do you manage microservices API versions and branching strategies?
Keep all API versions in the code Another strategy is to have all the different API versions in the same code. So you may have a folder structure that looks like this: api ├── v1 └── v2 Within the API folder, you have one folder for v1 and another one for v2. Each folder has its own schemas and routes as required by the API version they implement. If you use URL-based versioning, v1 is accessible through the example.com/v1 endpoint or the v1.example.com subdomain (whichever strategy you use), and same for v2. Deprecating a version is a simple as its corresponding folder. In any case, I'd recommend you also validate your API implementations in the CI using something like schemathesis. Schemathesis looks at the API documentation and automatically generates hundreds of tests to make sure you're using the right schemas, status codes, and so on. It works best if you design and document the API before implementing, which allows you to include OpenAPI links and other features.
-
This Week in Python
schemathesis – Run generated test scenarios based on your OpenAPI specification
What are some alternatives?
Mimesis - Mimesis is a robust data generator for Python that can produce a wide range of fake data in multiple languages.
dredd - Language-agnostic HTTP API Testing Tool
FauxFactory - Generates random data for your tests.
Robot Framework - Generic automation framework for acceptance testing and RPA
fake2db - create custom test databases that are populated with fake data
pytest - The pytest framework makes it easy to write small tests, yet scales to support complex functional testing
picka - pip install picka - Picka is a python based data generation and randomization module which aims to increase coverage by increasing the amount of tests you _dont_ have to write by hand.
coverage
PyRestTest - Python Rest Testing
drf-openapi-tester - Test utility for validating OpenAPI documentation
radar
tox - Command line driven CI frontend and development task automation tool.