gomatch alternatives and similar packages
Based on the "Testing Frameworks" category.
Alternatively, view gomatch alternatives based on common mentions on social networks and blogs.
-
-
-
dockertest
Write better integration tests! Dockertest helps you boot up ephermal docker images for your Go tests with minimal work. -
-
-
-
gnomock
Test your code without writing mocks with ephemeral Docker containers 📦 Setup popular services with just a couple lines of code ⏱️ No bash, no yaml, only code 💻 -
-
-
-
-
embedded-postgres
Run a real Postgres database locally on Linux, OSX or Windows as part of another Go application or test -
gotest.tools
A collection of packages to augment the go testing package and support common patterns. -
go-testdeep
Extremely flexible golang deep comparison, extends the go testing package, tests HTTP APIs and provides tests suite -
testza
Full-featured test framework for Go! Assertions, fuzzing, input testing, output capturing, and much more! 🍕 -
-
-
-
GoSpec
Testing framework for Go. Allows writing self-documenting tests/specifications, and executes them concurrently and safely isolated. [UNMAINTAINED] -
jsonassert
A Go test assertion library for verifying that two representations of JSON are semantically equal -
assert
:exclamation:Basic Assertion Library used along side native go testing, with building blocks for custom assertions -
-
-
-
-
-
gogiven
gogiven - BDD testing framework for go that generates readable output directly from source code
InfluxDB - Purpose built for real-time analytics at any scale.
Do you think we are missing an alternative of gomatch or a related project?
README
Gomatch
Library created for testing JSON against patterns. The goal was to be able to validate JSON focusing only on parts essential in given test case so tests are more expressive and less fragile. It can be used with both unit tests and functional tests.
When used with Gherkin driven BDD tests it makes scenarios more compact and readable. See Gherkin example
Contests
Installation
go get github.com/jfilipczyk/gomatch
Basic usage
actual := `
{
"id": 351,
"name": "John Smith",
"address": {
"city": "Boston"
}
}
`
expected := `
{
"id": "@number@",
"name": "John Smith",
"address": {
"city": "@string@"
}
}
`
m := gomatch.NewDefaultJSONMatcher()
ok, err := m.Match(expected, actual)
if ok {
fmt.Printf("actual JSON matches expected JSON")
} else {
fmt.Printf("actual JSON does not match expected JSON: %s", err.Error())
}
Available patterns
@string@@number@@bool@@array@@uuid@@email@@wildcard@@...@- unbounded array or object
Unbounded pattern
It can be used at the end of an array to allow any extra array elements:
[
"John Smith",
"Joe Doe",
"@...@"
]
It can be used at the end of an object to allow any extra keys:
{
"id": 351,
"name": "John Smith",
"@...@": ""
}
Gherkin example
Gomatch was created to use it together with tools like GODOG. The goal was to be able to validate JSON response focusing only on parts essential in given scenario.
Feature: User management API
In order to provide GUI for user management
As a frontent developer
I need to be able to create, retrive, update and delete users
Scenario: Get list of users sorted by username ascending
Given the database contains users:
| Username | Email |
| john.smith | [email protected] |
| alvin34 | [email protected] |
| mike1990 | [email protected] |
When I send "GET" request to "/v1/users?sortBy=username&sortDir=asc"
Then the response code should be 200
And the response body should match json:
"""
{
"items": [
{
"username": "alvin34",
"@...@": ""
},
{
"username": "john.smith",
"@...@": ""
},
{
"username": "mike1990",
"@...@": ""
}
],
"@...@": ""
}
"""
License
This library is distributed under the MIT license. Please see the LICENSE file.
Credits
This library was inspired by PHP Matcher
Logo
The Go gopher was designed by Renee French. (http://reneefrench.blogspot.com/). Gomatch logo was based on a gopher created by Takuya Ueda (https://twitter.com/tenntenn). Licensed under the Creative Commons 3.0 Attributions license. Gopher eyes were changed.
*Note that all licence references and agreements mentioned in the gomatch README section above
are relevant to that project's source code only.