Releases: for-GET/katt
Releases · for-GET/katt
1.5.0 release candidate
Breaking changes:
- KATT CLI defaults now to showing only the last transaction, but understands
--all
for previous behaviour #31 - new Erlang pattern that includes error details #25
Notable changes (since 1.4.0):
- textual diff for strings #20 (new Erlang pattern that includes error details)
- added
runtime_value
andruntime_validation
#29 - KATT CLI can now convert an HTTP Archive to an APIB file, making it easier to create scenarios
- allow
katt:run
to take in a#katt_blueprint
record, not just a path to an APIB file - switched lhttpc for hackney #17
- switched mochijson3 for jsx
1.4.0
Breaking changes:
Notable changes (since 1.3.0):
- handle duplicate headers #14
- handle request timeout #13
- fix katt compilation as rebar dependencies #24
Full list of changes since 1.3.0
Full list of changes since 1.3.1-rc
1.3.1 release candidate
1.3.0
Notable changes (since 1.2.6):
- standalone katt executable (with Erlang/JSON output)
- progress output to stderr
- complex/multiple store (match and store a substring in a param)
- storing is optional as one can use {{_}} to match any substring
- support complex validations via a special
{ "{{type}}": "....", "type_specific_arg1": ..., ... }
pattern- built-in
set
comparison - JSON array with no specific order
- built-in
- extensions (XML example in README)
- progress callback
- request timeout and transaction description can be set via HTTP request headers
- request can be delayed (put to sleep) via HTTP request header
- optimized, refactored, moved shit around, fixed bugs
Full list of changes since 1.2.6
Full list of changes since 1.3.0-rc
1.3.0 release candidate
Since there are quite a few changes from the previous version - 1.2.6 - here's a release candidate, in order to collect feedback.
Would be great if you can upgrade to this tag, and run your current scenarios to see any adverse effects. I don't think there should be any.
Notable changes:
- katt executable (escript)
- complex/multiple store (match and store a substring in a param)
- support complex validations via a special
{ "{{type}}": "....", "type_specific_arg1": ..., ... }
pattern- built-in
set
comparison - JSON array with no specific order - see validate_type_set branch waiting to be merged
- built-in
- extensions (XML example in README)
- progress callback
- optimized, refactored, moved shit around