The zato-apitest based test regime for Gaskata.
Stars
0
Forks
0
Watchers
0
Open Issues
0
Overall repository health assessment
No package.json found
This might not be a Node.js project
17
commits
When the request fails, there is a very hich chance that the response text is not in the same format as the request format set. Which results in very little response information. If I use the raw data.text, I will get whatever the server sent. Which is alot more useful. Hopefully.
f0ccf8aView on GitHubAs the added comment says. we might have reset the context before we print the doc..
25498a4View on GitHubThis looks better. Now We have two environment options, one for printing DOC on passed, and the other for a filename. I guess I could use only one and kinda have "stdout" and "stderr" as defaults for oute and the rest for filenae..
0b688efView on GitHubCardinal sin! Forgot to 1) put config.ini in .gitignore, 2) make a config.ini-dist file.
7ee982cView on GitHubPretty simple steps, check if a text is included in the (raw) response.
5c1f4f2View on GitHubNo need to print doc, nor verbose output when something fails, it's printed upfront if the user wants it. (Which you tend to want if you want verbose output..)
025d24eView on GitHubForgot I had moved the doc wrting from after feature to after scenarion, where it belongs if you want to write doc for all calls.
91f91a2View on GitHubAdding yet another test, checking of we fail on missing user credentials, but sending a password.
8968269View on GitHubAdded the three setting variables to the README and changed from after_feature to the correct after_scenario for debug and doc.
8efc1f1View on GitHub