pact-js
zod
Our great sponsors
pact-js | zod | |
---|---|---|
9 | 288 | |
1,546 | 30,347 | |
1.4% | - | |
8.7 | 9.1 | |
6 days ago | 3 days ago | |
TypeScript | TypeScript | |
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.
zod
-
From Flaky to Flawless: Angular API Response Management with Zod
Zod is an open-source schema declaration and validation library that emphasizes TypeScript. It can refer to any data type, from simple to complex. Zod eliminates duplicative type declarations by inferring static TypeScript types and allows easy composition of complex data structures from simpler ones. It has no dependencies, is compatible with Node.js and modern browsers, and has a concise, chainable interface. Zod is lightweight (8kb when zipped), immutable, with methods returning new instances. It encourages parsing over validation and is not limited to TypeScript but works well with JavaScript as well.
- TypeScript Essentials: Distinguishing Types with Branding
-
You can’t run away from runtime errors using TypeScript
Zod is a TypeScript-first schema declaration and validation library. It helps create schemas for any data type and is very developer-friendly. Zod has the functional approach of "parse, don't validate." It supports coercion in all primitive types.
-
Best Next.js Libraries and Tools in 2024
Link: https://zod.dev/
-
Popular Libraries For Building Type-safe Web Application APIs
You can check out their documentation here.
-
Epic Next JS 14 Tutorial Part 4: How To Handle Login And Authentication in Next.js
You can learn more about Zod on their website here.
-
What even is a JSON number?
In JS, it's a good idea anyway to use some JSON parsing library instead of JSON.parse.
With Zod, you can use z.bigint() parser. If you take the "parse any JSON" snippet https://zod.dev/?id=json-type and change z.number() to z.bigint(), it should do what you are looking for.
-
Error handling in our form component for the NextAuth CredentialsProvider
We will validate our input using client-side zod. Zod handles TypeScript-first schema validation with static type inference. This means that it will not only validate your fields, it will also set types on validated fields.
-
Zod: Zero to Hero - Chapter 4
A word of warning: while discriminated unions are very powerful, there's an ongoing discussion on whether discriminated unions should be deprecated and replaced with a different API.
-
Zod: Zero to Hero - Chapter 1
I was first introduced to Zod by Adam Bobrow - a colleague of mine and a dear friend. Adam was sick and tired from JavaScript's brittleness, and about two years ago he started migrating our code base to TypeScript. But that wasn't enough for him. He kept complaining: "What good are my types, if some other service decides to send me bad data and breaks my code?". That's when he discovered Zod.
What are some alternatives?
Nock - HTTP server mocking and expectations library for Node.js
class-validator - Decorator-based property validation for classes.
Karate - Test Automation Made Simple
joi - The most powerful data validation library for JS [Moved to: https://github.com/sideway/joi]
rust-wildbow-scraper - Automatically scrapes wildbow's web serials and compiles them into ebooks
Yup - Dead simple Object schema validation
Robot Framework - Generic automation framework for acceptance testing and RPA
typebox - Json Schema Type Builder with Static Type Resolution for TypeScript
mockoon - Mockoon is the easiest and quickest way to run mock APIs locally. No remote deployment, no account required, open source.
ajv - The fastest JSON schema Validator. Supports JSON Schema draft-04/06/07/2019-09/2020-12 and JSON Type Definition (RFC8927)
io-ts - Runtime type system for IO decoding/encoding