Usage: go-mana-test [ -c ] COMMAND [arg...]
Making APIs Nice Again - Testing Framework
Options:
-c, --color Outputs console in color mode.
Commands:
version Shows version info.
validate Validate project and test files.
test Run tests.
Run 'go-mana-test COMMAND --help' for more information on a command.Usage: go-mana-test validate PATH
Validate project and test files.
Arguments:
PATH Path to project.You can validate your project and test files by using the validate command project file.
go-mana-test validate ./exampleproj/project.ymlUsage: go-mana-test test [-bhp] PATH
Run tests.
Arguments:
PATH Path to project.
Options:
-b, --bodies Outputs HTTP request and response bodies.
-e, --exit Exits on failed tests.
-p, --perf Reports HTTP response time performance.You can run your tests by using the test command project file.
go-mana-test test ./exampleproj/project.ymlThe bodies option can be added to output HTTP request and response bodies.
go-mana-test test -b ./exampleproj/project.ymlThe exit option can be added to exit when a test has failed.
go-mana-test test -e ./exampleproj/project.ymlThe perf option can be added to display HTTP response time calculations for each test, the overall average, the minimum, and maximum, response time.
go-mana-test test -p ./exampleproj/project.ymlThe project file setups your project. Here is an example project file.
name: My Sample Project
tests: ./tests
globals:
- key: USER_AGENT
value: go-mana-test
- key: LOCALE
value: en_us- name: Defines the name of your project.
- tests: Defines the path to your test files, relative to the path this project file is in.
- globals: Defines key/value global variables that can be later used in your tests.
The test file defines a single test for your project. Here is an example of a test file.
name: Update User Profile
index: 100
url: "https://api.sample.com/v1/profile"
params:
search: "gopher"
request.method: POST
request.headers:
- key: Content-Type
value: application/json
- key: User-Agent
value: "{{globals.USER_AGENT}}"
request.body:
username: john.doe
cache:
- name: user_profile.username
value: response.body.json.username
checks:
- name: Proper response code
check: response.code
value: 200
- name: Proper body for updated username
check: response.body.json.username
value: "{{cache.body.username}}"
- name: Has fav ID
check: response.body.json.favs.#[id=="{{cache.body.fav_id}}"].id
value: "{{cache.body.fav_id}}"- name: Defines the name of your test.
- url: Defines the URL to use in the test. This may make use of variables.
- params: Defines the parame for the URL query string. This may make use of variables.
- method: Defines the HTTP method to use for the test.
- index: Defines the index of the test. Lower value indexes will be run before higher value indexes.
- request.headers: Defines the HTTP headers to send in the test in key/value format.
- request.body: Defines the body to send in the test. If you are sending JSON https://www.json2yaml.com is a nice tool to help you convert JSON to YAML.
- cache: Defines cache to save from this test.
- checks: Defines the checks to validate in this test.
The params field takes an object that will get mapped to the URL query string. Values will be escaped using net/url Values. For example, given this abbreviated test file:
url: "https://api.sample.com/v1/profile"
params:
search: "gopher con"
method: GET
A GET request would be sent to https://api.sample.com/v1/profile?search=gopher+con.
Test cache is run before the [test checks][#test-checks]. Caching allows you to cache certain values that can cary onto the checks in your test file, or across all test files.
The test cache uses key/value methods to store data.
- name: Defines the name of your cache. Can be any string.
- value: Defines the value to cache. Can be any of the following:
- response.body.json: Refers the json body of the response. Anything following this prefix this will query methods of the json body.
Test checks are used to validate results of the test.
- name: Defines the name of your test. Can be any string.
- check: Defines the check to use. Can be any of the following:
- response.code: References response HTTP status code.
- response.body.json: Refers the json body of the response. Anything following this prefix will query methods of the json body, and may make use of variables.
- value: Defines the value to use in the test. This may make use of variables.
Variable substitution is helpful for certain properties of the test and project files. Inside of YAML files, replacements must always be enclosed inside of "". The full syntax is:
"{{variable.to.use}}Below are some of the variables that can be used:
Global variables are defined in the project file. The full syntax is:
"{{globals.MY_GLOBAL_VARIABLE}}"Can be used in:
- Test URL
- Test request header
- Test request body
- Test check value
For the sample project file above, referencing the User Agent would be:
"{{globals.USER_AGENT}}"Cache variables are defined in the test file. The full syntax is:
"{{cache.MY_CACHE_VARIABLE}}"Can be used in:
- Test URL
- Test request header
- Test request body
- Test check value
For the sample test file above, referencing the Username would be:
"{{cache.user_profile.username}}"Environment variables are defined on your Operating System. The full syntax is:
"{{env.MY_ENV_VARIABLE}}"Can be used in:
- Project globals
- Test URL
- Test request header
- Test request body
- Test check value
Generates a random alpha-numeric string of a certain length. The syntax to generate a string of length 50 is:
"{{rand.string.50}}"Can be used in:
- Project globals
- Test URL
- Test request header
- Test request body
- Test check value
Generates a random lowercase alpha-numeric string of a certain length. The syntax to generate a string of length 60 is:
"{{rand.string.lower.60}}"Can be used in:
- Project globals
- Test URL
- Test request header
- Test request body
- Test check value
Generates a random uppercase alpha-numeric string of a certain length. The syntax to generate a string of length 70 is:
"{{rand.string.upper.70}}"Can be used in:
- Project globals
- Test URL
- Test request header
- Test request body
- Test check value
Generates a random number in between a certain range. The syntax to generate a number between 1 and 100 is:
"{{rand.num.1.100}}"Can be used in:
- Project globals
- Test URL
- Test request header
- Test request body
- Test check value
A path is a series of keys separated by a dot. A key may contain special wildcard characters '*' and '?'. To access an array value use the index as the key. To get the number of elements in an array or to access a child path, use the '#' character. The dot and wildcard characters can be escaped with '\'.
{
"name": {"first": "Tom", "last": "Anderson"},
"age":37,
"children": ["Sara","Alex","Jack"],
"fav.movie": "Deer Hunter",
"friends": [
{"first": "Dale", "last": "Murphy", "age": 44},
{"first": "Roger", "last": "Craig", "age": 68},
{"first": "Jane", "last": "Murphy", "age": 47}
]
}"name.last" >> "Anderson"
"age" >> 37
"children" >> ["Sara","Alex","Jack"]
"children.#" >> 3
"children.1" >> "Alex"
"child*.2" >> "Jack"
"c?ildren.0" >> "Sara"
"fav\.movie" >> "Deer Hunter"
"friends.#.first" >> ["Dale","Roger","Jane"]
"friends.1.last" >> "Craig"
You can also query an array for the first match by using #[...], or find all matches with #[...]#.
Queries support the ==, !=, <, <=, >, >= comparison operators and the simple pattern matching % operator.
friends.#[last=="Murphy"].first >> "Dale"
friends.#[last=="Murphy"]#.first >> ["Dale","Jane"]
friends.#[age>45]#.last >> ["Craig","Murphy"]
friends.#[first%"D*"].last >> "Murphy"There's support for JSON Lines using the .. prefix, which treats a multilined document as an array.
For example:
{"name": "Gilbert", "age": 61}
{"name": "Alexa", "age": 34}
{"name": "May", "age": 57}
{"name": "Deloise", "age": 44}..# >> 4
..1 >> {"name": "Alexa", "age": 34}
..3 >> {"name": "Deloise", "age": 44}
..#.name >> ["Gilbert","Alexa","May","Deloise"]
..#[name="May"].age >> 57