The key changes include:

* New matchers: JSON schema, form parameters, multi-value parameters, etc. * Response templating: path parameters, global state functions and data randomization * New extension API and better observability capabilities * New extension capabilities including support for gRPC and GraphQL and the new global state management * Dropping Java 8 support

We're organizing the first-ever Hacktoberfest-program in WireMock, with online and in-person events, some special swag, an a focus on people improving API integration tests in the open source projects. Feedback and PRs are welcome!

Writing a client app for Hacker News? We have something that may help. After creatin an OpenAPI specification for Hacker News API hosted in Firebase, we documented a walkthrough of creating a mock specification that can be used in WireMock and WireMock Cloud

Would anyone be also interested in a public Hacker News API template on https://apis.guru/ and https://library.wiremock.org/ ?

We're working on a demo for Hacker News REST API mocking in the Android client integration tests, and as a part of it we've assembled an OpenAPI specification for its endpoints provided by Firebase. It's based on the existing documentation and examples. Feedback will be appreciated!

WTH is OpenAPI we use? OpenAPI is an open standard, originally inherited from Swagger. It can be used to serve the docs on the website, IDE integrations, to generate client code and to create various API mocks for the integration tests.

If you want to generate a Java client for testing, you can use Fern to generate one: https://github.com/fern-api/fern-java

disclaimer: I'm a maintainer of Fern.

Yeah, there are many projects for client generation from OpenAPI, and the number keeps growing. Make sure to add your tool to https://tools.openapis.org/ !

Looking for feedback on WireMock and Testcontainers usage for API integration testing! Check out the early talk from Oleg Nenashev at the Java.IL meetup. Now we provide Java, Golang and Python integrations, more to be added soon!

Would WireMock on Testcontainers be interesting to you? What features would you like to see there?

Check out WireMock Chaos! It’s our latest add-on to WireMock Cloud which merges the power of API Mocking with Chaos Engineering to simulate API request failures. Hence, you can have better integration test coverage and ensure slow weekends for your platform engineers and maybe yourself when on-call :-)

Want to inject some chaos into your testing? WireMock Cloud has a ready to go “Hello world!” example in the quickstart. If you have an OpenAPI/Swagger definition ready, you can easily import it and bootstrap API in a few clicks. There is a free tier available for small projects and those who want to try it out.

For chaos testing, once APIs are defined, just open the Mock API, go to the “Chaos” configuration tab and toggle “Enable chaos”. There you can configure error rates, HTTP return codes and their distribution, as well as random long delays and timeouts. Then it will get applied to all the responses within the scope of the API.

Let us know what you think here or on the WireMock Slack: https://slack.wiremock.org/! And bring order to you API test chaos

We follow the Moonwalk project in WireMock, because the new features clearly provide some opportunities for better API integration testing and request/response validation that us now embedded in WireMock 3 Beta.

Our TL;DR: the standard looks interesting, the developer tools need a lot of love. The whole world is using JSON/YAML these days, but developer experience for JSON Schema is lightyears behind "legacy" XSD

I'll repeat a relevant bit from an earlier reply of mine:

The ideal system, to me (speaking as the most prolific contributor to JSON Schema drafts-07 through 2020-12), would have clearly defined code generation and runtime validation features that did not get in each other's way. Keywords like "anyOf" and "not" are very useful for runtime validation but should be excluded from type definition / code generation semantics.

This would also help balance the needs of strongly typed languages vs dynamically typed languages.

The fundamental problem is that JSON Schema was designed as a constraint validation system (https://modern-json-schema.com/json-schema-is-a-constraint-s...) and it's been overloaded for type definition in ways that don't always make sense. But the JSON Schema alternatives that I've seen go too far in the other direction. There is a lot of value in being able to perform more complex runtime validation in a language-independent way.

There is a balance and clear separation of concerns needed between data definition and runtime validation, although they still should live in the same contract as there is considerable overlap. Now if I could only find someone who wants to fund the design of such a system... :-)

Hello and bonjour! My name is Oleg Nenashev, I am representing the WireMock community and WireMock Inc here. If you have ever used Jenkins, most likely you've seen my name before. Sorry not sorry ;-) I have recently joined WireMock to help with growing its open source community and ecosystem beyond Java. FWIW I keep hacking too, e.g. the recent Testcontainers Java module for WireMock. But my main job is Dev Rel and community stuff, so here I am.

If you use Java, .NET or other tech stacks, most likely you've already tried WireMock for different API Mocking and integration testing use-cases. Maybe you tried one of dozens different implementations and adapters, of various quality IMHO. I'm currently assembling the roadmap for WireMock 3.0, documentation and the ecosystem. Would love to get your feedback about what works and what you'd like to see in the project.

Let me know what your experiences are! Our Slack is also open 24/7 for detailed feedback and live discussions