pact-js
Karate
Our great sponsors
pact-js | Karate | |
---|---|---|
9 | 25 | |
1,546 | 7,846 | |
1.4% | 1.3% | |
8.7 | 8.5 | |
7 days ago | 7 days ago | |
TypeScript | Java | |
GNU General Public License v3.0 or later | 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-js
-
Enhancing Backend Microservices Ecosystem with Contract Testing [Spartans Summit 2024]
First, he shows the official pact.io websites. Then, he clicks on the “View on Github” button by selecting Node JS and Javascript from the list of options.
-
Parsing AWS AppSync Responses, Elm GraphQL Libraries, and Only Doing Front-End
It just just enough abstraction over the basics of converting your HTTP calls to GraphQL queries and mutations, but ALL of the parsing of responses is on you. I’m well versed in parsing JSON in Elm. I’m also familiar with the compiler errors as well as runtime errors you get with JSON that doesn’t match up to what you designed. At some point I’ll probably have to move beyond the unit tests and add contact tests, maybe via Pact.js.
-
The Big TDD Misunderstanding
> I also wasn't aware that "unit" referred to an isolated test, not to the SUT.
I'm with you. That claim is unsubstantiated. It seems to trace to the belief that the first unit tests were XUnit family, thus were SUnit for Scheme. But Kent Beck made it pretty clear that SUnit "units" were classes.
https://web.archive.org/web/20150315073817/http://www.xprogr...
There were unit tests before that. SUnit took its name from common parlance, not vice versa. It was a strange naming convention, given that the unit testing framework could be used to test anything and not just units. Much like the slightly older Test Anything Protocol (TAP) could.
> [on unit tests] This does lead to a lot of work maintaining them whenever the implementation changes, but this is a necessary chore because of the value they provide.
I disagree. Unit tests can still be behavioral. Then they change whenever the behavior changes. They should still work with a mere implementation change.
> This is why I still think that the traditional test pyramid is the best model to follow.
I'll disagree a little with that, too. I think a newer test pyramid that uses contract testing to verify integrations is better. The notion of contract tests is much newer than the pyramids and, properly applied, can speed up feedback by orders of magnitude while also cutting debugging time and maintenance by orders of magnitude.
On that front, I love what Pact is doing and would like to see more competition in the area. Hottest thing in testing since Cypress/Playwright . . .
https://pact.io
-
Ask HN: How do you test your microservices?
I've worked in places where Pact [0] was used for testing services developed by different teams (external) and teams themselves (internal)
[0] https://pact.io/
-
A response to James Shore's Nullable pattern
I'd never heard anyone call those "integrity tests" before. I think "contract test" is more common.
Assuming I understood you, that is.
I've been telling everyone to look at Pact to make contract testing easier to organize and maintain and to make it easier to trigger in the other tests in CI when an interface's behavior changes. They haven't offered me a commission yet. ;-)
https://pact.io
- Gestionarea DTO-urilor intr-o arhitectura de tip Microservicii cu Event-Driven
-
Can someone recommend technologies for testing automation for API application?
We use pact and since introducing it we have significantly increased velocity and reduced test cycles as it catches things very early. For system tests we hand write them using whatever test frameworks the team is used to.
-
Advanced TypeScript Patterns: API Contracts
There is also Pact https://pact.io/ for a language agnostic pact testing.
-
Framework for end to end testing of microservices
When you wish to focus on the contract ( which kind of field is required, ...), you shoud use contract testing frameworks. As you seem to leverage a microservices, a consumer driven contract testing approach with a framework like Pact.js is recommended.
Karate
-
Cucumber Maintainer out of Job and future of the project is uncertain
This is why we need better tools which will give benefits for the added complexity. If you need to create both the feature files AND the code, it's just complexity with little benefits. But frameworks like https://github.com/karatelabs/karate or https://github.com/Endava/cats are hiding this complexity and remove the code layer entirely. Which, in my view, this is where you need to be in 2023, particularly for API testing.
-
Need a fully local web alternative to Postman
- https://insomnia.rest/ - https://hoppscotch.io/ - https://github.com/karatelabs/karate - https://github.com/warmuuh/milkman
-
Lama2: Plain-Text Powered REST API Client for Teams
Congrats on the launch ! I'm the lead dev of [Karate](https://github.com/karatelabs/karate) and was wondering if you had come across it. I strongly agree that collaboration should be [via Git](https://www.karatelabs.io/first-class-citizens) and the IDE and traditional solutions fall short. I hope Karate's syntax passes your "memory friendly" test :) We get regular feedback is that it is easy to read and even non-programmers can pick it up. One thing I feel we do really well is chaining of HTTP requests. And we have plugins for [IntelliJ](https://plugins.jetbrains.com/plugin/19232-karate) and [VS Code](https://marketplace.visualstudio.com/items?itemName=karatela...).
Maintaining a tool like this as open-source is hard, all the best !
- Interview
- Hurl, run and test HTTP requests with plain text
-
Hurl 1.8.0, text based integration tests for REST APIs and web sites
FWIW https://github.com/karatelabs/karate is 83% Java.
- Best tool for automated API e2e testing
-
Automated testing
We use karate to test our fully integrated graphql backend. Has Gherkin language support.
-
What is the best self hosted API-testing tool in 2022 ?
Try Karate
-
Framework for end to end testing of microservices
Take a look at Karate.
What are some alternatives?
Nock - HTTP server mocking and expectations library for Node.js
REST Assured - Java DSL for easy testing of REST services
rust-wildbow-scraper - Automatically scrapes wildbow's web serials and compiles them into ebooks
Apache JMeter - Apache JMeter open-source load testing tool for analyzing and measuring the performance of a variety of services
zod - TypeScript-first schema validation with static type inference
WireMock - A tool for mocking HTTP services
Robot Framework - Generic automation framework for acceptance testing and RPA
Cucumber - Cucumber for the JVM
mockoon - Mockoon is the easiest and quickest way to run mock APIs locally. No remote deployment, no account required, open source.
Selenium
io-ts - Runtime type system for IO decoding/encoding
MockServer - MockServer enables easy mocking of any system you integrate with via HTTP or HTTPS with clients written in Java, JavaScript and Ruby. MockServer also includes a proxy that introspects all proxied traffic including encrypted SSL traffic and supports Port Forwarding, Web Proxying (i.e. HTTP proxy), HTTPS Tunneling Proxying (using HTTP CONNECT) and SOCKS Proxying (i.e. dynamic port forwarding).