Releases: Endava/cats
Releases · Endava/cats
v5.2.7
Release notes:
- Headers Fuzzers are not considering auth headers anymore
- Fix issue in report when clicking outside the test status filter levels causing the list of tests to display empty
- Change the order of displaying the Fuzzer name in individual Test Cases in order to accommodate global Fuzzers cases
v5.2.6
Release notes:
- Fix issue with auth headers not being recognised when not matching full name from pre-defined list
- Fix issue with Fuzzer names not being properly displayed in report after latest logback pattern change
v5.2.5
Release Notes:
- Fix issue with
additionalPropertieshaving nestedadditionalPropertiesof type object - Fix issue with auth headers not always being parsed correctly
v5.2.4
Release Notes:
- make CATS proxy aware by using
--proxyHostand--proxyPort - change logging to use https://github.com/ludovicianul/pl4j
- make Fuzzer names shorter when prefixing log line by only using the first character of every work from their class name
v5.2.3
v5.2.2
Release notes:
- Fix an issue when a response was an array and CATS didn't properly check if the elements match the declared schema
- Whitelist the
body_JSON objects names generated by OpenAPI in order to not be labeled incorrectly by the Contract fuzzers - Allow JSON object names to also match
snake_caseandhyphen-case - Allow
refDatato contain fields which can be marked for removal usingcats_remove_field
v5.2.1
Release notes:
- custom files now use JsonPath syntax, so you have more control on the properties being replaced/used
- fix for
SpacesOnlyInFieldsTrimValidateFuzzerbeing ignored when the fuzzers where running - introduce arguments like
--checkHeaders,--checkFieldsor--checkContractto be able to run only categories of fuzzers
v5.2.0
Release Notes:
- fix various issues when dealing with
oneOforallOfelements - add new Fuzzers for checking OpenAPI contract good practices in terms of presence of specific elements, naming conventions, content types, recommended headers
- fix issue when CATS was considering a
404a valid response for validation error; it now expects400or422 - CATS now also checks if the fuzzedField is present in a validation error response
- allow
org.apache.commons.lang3classes to be used via SPeL in configuration files such as refData, customFuzzer, etc - fix issue with
--printExecutionStatisticswas only considering SKIPPED tests - fix for elements sometimes not being displayed in the proper order in the final report
v5.1.1
Release notes:
- Add the possibility to add
additionalPropertiesinsiderefDataandcustomFuzzerFile - Add possibility to supply dynamic values to
refData,customFuzzerFileandsecurityFuzzerFile. Currently it supports only thejava.timepackage - Update Report summary to also includes the path
v5.1.0
Release Notes:
- fix for
HttpMethodsFuzzernot conditioning HEAD by GET requests - Add 2 new Fuzzers for exact value matching:
MinimumExactValuesInNumericFieldsFuzzerandMaximumExactValuesInNumericFieldsFuzzer - Add new security Fuzzers for checking security headers and mime types according to OWASP REST API recommendations
list fuzzerswill now list fuzzers based on categories: Field, Header and Http