elm-graphql
pact-js
elm-graphql | pact-js | |
---|---|---|
3 | 9 | |
777 | 1,561 | |
- | 1.5% | |
4.4 | 8.8 | |
4 months ago | 19 days ago | |
Elm | TypeScript | |
BSD 3-clause "New" or "Revised" License | GNU General Public License v3.0 or later |
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.
elm-graphql
-
Parsing AWS AppSync Responses, Elm GraphQL Libraries, and Only Doing Front-End
Once I could quickly make calls against a server, and see the raw responses were matching up to my expectations, I moved to finding an Elm equivalent. Two years ago or so, Dillon had his GraphQL library and marketed it well.
-
The REGAL Architecture
The elm-graphql library enables code generation. This enables us to extend the “fearless refactoring” across the entire stack. As we build, learn, and eventually change our domain model from those learning’s, we can regenerate the front-end code needed, and the compiler lets us know what to modify (I still haven’t found something this powerful for ReScript yet).
-
Easy Questions / Beginners Thread (Week of 2021-05-03)
I've managed to run the example from dillonkearns examples at master, however it is using a strange version of Swapi/Object with CustomScalarCodecs instead of ScalarCodecs generated by his code generation utility. I'm new to Elm, so costed me some time to make the Starwars.elm file work with properly generated classes, since even Id types in the repo example are not matching the generated types (Int vs String).
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.
What are some alternatives?
elm-visualization - A data visualization library for Elm
Nock - HTTP server mocking and expectations library for Node.js
elm-lang.org - Server and client code for the Elm website.
Karate - Test Automation Made Simple
rescript-compiler - The compiler for ReScript.
rust-wildbow-scraper - Automatically scrapes wildbow's web serials and compiles them into ebooks
r10 - R10 is a library of interactive building blocks written in Elm and elm-ui that we use at Rakuten for creating user interfaces.
zod - TypeScript-first schema validation with static type inference
elm-collage - Create interactive vector graphics and position them relative to each other
Robot Framework - Generic automation framework for acceptance testing and RPA
elm-pages-tailwind-starter - Starter for elm pages and tailwind.
mockoon - Mockoon is the easiest and quickest way to run mock APIs locally. No remote deployment, no account required, open source.