Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
dmitry_dygalo
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
1.
▲
by
dmitry_dygalo
10mo ago
Schemathesis author here. Feel free to open an issue if something does not work as you expect :) As a side note, if you'd like to check what is covered by Schemathesis or any other testing tool or manual tests, you may want to try htt
2.
▲
by
dmitry_dygalo
11mo ago
Hi! Author of Schemathesis here, really glad to hear it helped you uncover those edge cases. If any of those bugs were in public or open-source APIs, I’d love to feature them in our new “trophy case”: https://github.com/sche
3.
▲
Generating Open API Specs with Hypothesis
(dygalo.dev)
1 points
by
dmitry_dygalo
2y ago
|
0 comments
4.
▲
by
dmitry_dygalo
2y ago
Thanks! > Two suggestions: it’s not immediately obvious whether subsequent benchmark result tables/rows show deltas from the original approach or from the preceding one (it’s the latter, which is more impressive). Maybe call that ou
5.
▲
by
dmitry_dygalo
2y ago
> This article is disingenuous with its Vec benchmark. Each call to `validate` creates a new Vec, but that means you allocate + free the vec for each validation. Why not store the vec on the validator to reuse the allocation? Why not men
6.
▲
by
dmitry_dygalo
2y ago
That is really cool idea! Thank you
7.
▲
by
dmitry_dygalo
2y ago
This was my intention
8.
▲
by
dmitry_dygalo
2y ago
Easier to avoid allocation errors, e.g. in the Linux kernel. I think Alice Ryhl mentioned it here - https://www.youtube.com/watch?v=CEznkXjYFb4
9.
▲
by
dmitry_dygalo
2y ago
I'd say most developers don't write kernels/drivers or embeds, at least from what I've seen. I am not saying that there are not many devs like this, but rather that there are fewer kernel devs than web devs.
10.
▲
by
dmitry_dygalo
2y ago
Indeed, I agree with your points. This idea was added after I wrote the post and wasn't taken from my own optimization efforts in `jsonschema`. Originally, in `jsonschema` the output type is actually a badly composed iterator and I int
11.
▲
Fast linked lists
(dygalo.dev)
182 points
by
dmitry_dygalo
2y ago
|
127 comments
12.
▲
by
dmitry_dygalo
3y ago
I'd be happy to help, looking forward :)
13.
▲
by
dmitry_dygalo
3y ago
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/sche
14.
▲
by
dmitry_dygalo
3y ago
Hi! > Test feedback - during our TestGen flow, the user provides feedback on the sequence and contents of the API requests. So, it is not fully automated, the user needs to provide the feedback, or is it optional? Originally by feedback,
15.
▲
by
dmitry_dygalo
3y ago
Also, an important note would be that Schemathesis is a property-based testing tool, which does not necessarily imply load testing. I.e. the comparison might not be that helpful as tools have different goals. However, Schemathesis can use t
16.
▲
by
dmitry_dygalo
3y ago
Schemathesis author here. I hope to clarify a few points here > From my understanding, Schemathesis can generate data based on a value being a string, number, boolean, etc Schemathesis can generate data that matches the spec or not based
17.
▲
by
dmitry_dygalo
3y ago
This reminds me of several solutions albeit lacking the explicit "AI" part: - Up9 observes traffic and then generates test cases (as Python code) & mocks - Dredd is built with JavaScript, runs explicit examples from the Open A
18.
▲
by
dmitry_dygalo
4y ago
Hi, Schemathesis author here I'd add that Schemathesis is essentially a fuzzer, where from the first glance Step CI is not (correct me if I am wrong).
19.
▲
by
dmitry_dygalo
4y ago
Hi Juan! Likewise :) Thank you! That's a great point! Added to the backlog :) Most of the machinery is provider-independent on the Schemathesis side, so adding a new provider should be relatively straightforward. I'll take a look
20.
▲
Show HN: Open API and GraphQL Fuzzing via GitHub Actions
(github.com)
3 points
by
dmitry_dygalo
4y ago
|
3 comments
21.
▲
by
dmitry_dygalo
4y ago
The `jsonschema` crate author here. First of all, this is an exciting use case, I didn't even anticipate it when started `jsonschema` (it was my excuse to play with Rust). I am extremely pleased to see such a Postgres extension :) At t
22.
▲
Generating arbitrary queries for a GraphQL schema
(github.com)
3 points
by
dmitry_dygalo
4y ago
|
0 comments
23.
▲
Deriving Semantics-Aware Fuzzers from Web API Schemas
(arxiv.org)
2 points
by
dmitry_dygalo
5y ago
|
0 comments
24.
▲
by
dmitry_dygalo
5y ago
And from GraphQL APIs as well :)
25.
▲
Using Hypothesis and Schemathesis to Test FastAPI
(testdriven.io)
2 points
by
dmitry_dygalo
6y ago
|
0 comments
26.
▲
Fuzz Testing of REST API
(research.redhat.com)
2 points
by
dmitry_dygalo
6y ago
|
0 comments
27.
▲
Schemathesis: Property-based testing for API schemas
(code.kiwi.com)
3 points
by
dmitry_dygalo
7y ago
|
0 comments
28.
▲
A tool for testing web applications built with Open API / Swagger
(github.com)
12 points
by
dmitry_dygalo
7y ago
|
0 comments
29.
▲
Good and bad practices for writing testable code
(code.kiwi.com)
3 points
by
dmitry_dygalo
8y ago
|
0 comments