Pact JVM
msw
Pact JVM | msw | |
---|---|---|
25 | 148 | |
1,058 | 14,848 | |
0.6% | 1.4% | |
8.9 | 9.2 | |
9 days ago | 4 days ago | |
Kotlin | TypeScript | |
Apache License 2.0 | 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.
Pact JVM
-
Running tests against a different repository (CI/CD)
API Contract Testing might be worth exploring. Gives you the ability to run it quickly locally or in CI/CD. A centralized way to validate if your changes broke another service might also be interesting. That series of videos from the same team is gold: https://docs.pact.io
-
API testing for new project (new to APIs)
We use Pact for contract testing https://docs.pact.io/
-
Why I will stop mocking for most of my Unit Tests in a Spring-Boot Application
The introduction here is quite good: https://docs.pact.io/
-
Does anyone know how to do an integration test on microservices build with asp core?
Pact.Net documentation: https://docs.pact.io/ Mountebank documentation: http://www.mbtest.org/ The Microsoft.AspNetCore.TestHost package on GitHub: https://github.com/aspnet/AspNetCore/tree/main/src/Testing/Microsoft.AspNetCore.TestHost
-
Integration testing best practices for API servers...
There's also https://docs.pact.io/ but I haven't had time yet to really look into it but probably someone else can tell something about it.
-
🤝 Contract Testing with Pact
This PoC shows a step by step implementation of contract testing using Pact.
-
Operation Pact or: How I Learned to Stop Worrying and Love Contract Testing
Contract tests assert that inter-application messages conform to a shared understanding documented in a contract. Without contract testing, the only way to ensure that applications will work correctly together is by using expensive and brittle integration tests.
-
How to Share API Changes with Your Team
If you are updating your API based on user feedback, you can work with your team or stakeholders to build an API contract describing how your API should function. You can use JSON schemas to document your API’s endpoint response codes and set up the contract. The contract must be accepted by all parties. Then, any changes made to the API must pass the contract test before being approved. Contract testing can be automated and incorporated into your CI/CD pipeline. Contract testing tools include Pact and Spring Cloud Contract.
-
Book notes: Turn the Ship Around!
Pact.
-
I have difficulties in unit testing
I have contract tests (https://docs.pact.io/) to ensure the integration works.
msw
-
Easier TypeScript API Testing with Vitest + MSW
However, I discovered a great combination that transformed my API call testing in TypeScript: Vitest and Mock Service Worker (MSW). Their well-crafted design makes them incredibly easy to use, enhancing the overall testing experience.
-
Creating mocks for testing react code
While mocks are effective, they require modifying the component's internal logic or mocking global functions like fetch. This can become cumbersome for complex components with numerous API interactions. Here's where MSW shines.
-
Storybook 8
> For those wondering what the use case is, you must not have tried it. It does take work to set up (with each version that's less), but it can be very nice to test in isolation esp in cases where a component is under a login, the 4th page of a 10 page form, etc. Also obviously if you're working on a component library that ships without an app, Storybook can be your development and/or demo app.
I have worked with storybook extensively over the past couple of years and my team is moving away from it in favour of MSW (https://mswjs.io).
For "4th page of a 10 page form" during the development there's hot reloading which is really stable nowadays and haven't failed me, although I understand that some setups are old and it might be easier to configure Storybook than good hot reloading.
I'm not entirely sure about the testing part of it and I'd be grateful if you could elaborate. I haven't felt the need for some special setup with SB because for unit tests, I can test a deeply nested component separately. For E2E tests, I usually test the whole form.
I agree on the component library part, this is probably the only use case where Storybook is 100% justified, but I'm unconvinced about the
Additionally, thank you to all our community launch partners across the frontend ecosystem for helping us bring Storybook 8 to the world! Thanks to Chromatic, Figma, ViteConf, Omlet, DivRiots, story.to.design, StackBlitz, UXpin, Nx, Mock Service Worker, Anima, Zeplin, zeroheight, kickstartDS, and Kendo UI.
-
I made "TypeScript Swagger Editor", new type of Swagger UI writing TypeScript code in the browser
similar with msw.js, but fully automated
-
Partial: how not to mock the whole world
they could be network mocks (use msw)
-
How to Automatically Consume RESTful APIs in Your Frontend
With orval, we can also integrate the API client in our unit tests. Orval provides first class support for mocking through the (Mock Service Worker)[https://mswjs.io/] library, and it can automatically generate the MSW handlers for testing server.
- Polly.js – Record, replay, and stub HTTP interactions
-
How to Successfully Integrate with Legacy APIs Using NodeJS
Consider a hypothetical scenario where data from a list of companies within an ERP needs to be retrieved. As a personal recommendation, leverage tools like MSW for top-level mocks, which can significantly enhance the testing process.
- How do you manage Dependency Injection in Next.js APPS?
What are some alternatives?
WireMock - A tool for mocking HTTP services
Nock - HTTP server mocking and expectations library for Node.js
REST Assured - Java DSL for easy testing of REST services
rtk-query - Data fetching and caching addon for Redux Toolkit
Testcontainers - Testcontainers is a Java library that supports JUnit tests, providing lightweight, throwaway instances of common databases, Selenium web browsers, or anything else that can run in a Docker container.
miragejs - A client-side server to build, test and share your JavaScript app
Mockito - Most popular Mocking framework for unit tests written in Java
mockoon - Mockoon is the easiest and quickest way to run mock APIs locally. No remote deployment, no account required, open source.
Cucumber - Cucumber for the JVM
prism - Turn any OpenAPI2/3 and Postman Collection file into an API server with mocking, transformations and validations.
Karate - Test Automation Made Simple
axios - Promise based HTTP client for the browser and node.js