JSONAssert
ts-pattern
Our great sponsors
JSONAssert | ts-pattern | |
---|---|---|
2 | 38 | |
963 | 10,882 | |
0.1% | - | |
0.0 | 8.5 | |
8 months ago | 14 days ago | |
Java | 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.
JSONAssert
-
Unit Testing Backward Compatibility of Message Format
And finally, we check that the supplied json equals to the one we got on step 3 (I use JSONAssert library here). The false boolean parameter tells to check only overlapping fields. For example, if the actual result contains the addressV2 field and the expected object doesn’t, it won’t trigger the failure. That’s a normal situation because backward compatibility data is static while the OrderCreated might grow with new parameters.
-
Stop requiring only one assertion per unit test: Multiple assertions are fine
This can be improved, it'd be worth Googling for a better solution than what you have.
https://github.com/skyscreamer/JSONassert seems decent.
but it can be done from scratch in a few hours (I'd recommend this if you have 'standardized' fields which you may want to ignore):
1) Move to a matcher library for assertions (Hamcrest is decent), and abstract `toJSON` into the a matcher, rather on the input.
This would change the assertion from:
`assertEquals(toJson(someObject), giantJsonBlobFromADifferentFile)`
to:
`assertThat(someObject, jsonEqual(giantJsonBlobFromADifferentFile))`
The difference here is subtle: it allows `jsonEqual` to control the formatting of the test failure output, so on a failure you can:
* convert both of the strings back to JSON
* perform a diff, and provide the diff in the test output.
Decent blog post on the topic: https://veskoiliev.com/use-custom-hamcrest-matchers-to-level...
ts-pattern
-
You Don't Need React
ts-pattern has been a decent band-aid for the lack of native pattern matching, but obviously has downsides that could be avoided if it was built into the language.
https://github.com/gvergnaud/ts-pattern
- Stop nesting ternaries
-
Building React Components Using Unions in TypeScript
ts-pattern
- Pattern Matching Library for TypeScript
-
TypeScript Is Surprisingly OK for Compilers
With how powerful the type system is you can implement pattern matching via a library pretty convincingly, https://github.com/gvergnaud/ts-pattern is definitely the go-to. That being said pattern matching is hardly a requirement for being ok for implementing compilers.
-
How to achieve type safety here possible without "type hacks"?
https://github.com/gvergnaud/ts-pattern might help
- ts-pattern v5
-
[AskJS] C# in every Node.js job posting?
There's a proposal to add something like that to JavaScript but it's been stuck in limbo since 2017 although there are libraries like ts-pattern which implement it already.
- Simplifying Dynamic Classes in Vue with the class-variance-authority library | cdruc.com
- Rust Appreciation Thread
What are some alternatives?
Spock - The Enterprise-ready testing and specification framework.
pattern-grab - 🤛🏻 Regular Expression Data Grabber
AssertJ - AssertJ is a library providing easy to use rich typed assertions
ts-adt - Generate Algebraic Data Types and pattern matchers
Hamcrest - Java (and original) version of Hamcrest
await-to-js - Async await wrapper for easy error handling without try-catch
TestNG - TestNG testing framework
union-types - A Typescript library for creating discriminating union types.
REST Assured - Java DSL for easy testing of REST services
ts-option
Mockito - Most popular Mocking framework for unit tests written in Java
typescript-coverage-report - Node command tool to generate TypeScript coverage report