PyRestTest v1.6.0 Release Notes
Release Date: 2015-10-12 // over 8 years ago-
🔋 Features:
- ✅ BETA: Add a type testing comparator to assist with validating request/header bodies
- Issue: https://github.com/svanoort/pyresttest/issues/90 (derived from online feedback)
- BETA: Allow setting custom Curl options with the curl_option_optionname field on tests
- 👍 BETA: support HTTP method types besides GET/PUT/POST/DELETE
- 👍 BETA: support setting request body on all request types, if present
- Allows (for example) DELETE methods that set a request body
- Caveat: does not set length if 0
- raw_body extractor that returns the full HTTP response body
- Requested in: https://github.com/svanoort/pyresttest/pull/71
- ➕ Add test coverage script (uses 'coverage', which requires install)
🛠 Bugfixes:
- 🛠 Fix bug with headers not being passed to extract_bind extrators, which caused:
- ✅ Extractors did not raise an exception on failure: https://github.com/svanoort/pyresttest/issues/64
- 🛠 Fix issue with use of curl WRITEDATA opt on CentOS 6 / Python 2.6 (use writefunction instead)
- 🛠 Fix/document installation issues with dependencies
Known Issues / Back-Compatibility:
- Minor: generator letters/uppercase/lowercase are now always ASCII, not locale-aware
- Driven by python 3 compatibility, and probably more "correct" but still a change
- Headers are now lists of (key, value) pairs, extractors need to be aware of this
- Will only be an issue for people using custom header extractors
- After some serious googling, as far as I can tell, nobody is using headers in custom extensions yet
- This can be patched into a back-compatibile approach if it breaks anyone
Misc:
- 🐳 Automation start (Jenkins setup, initial testing Dockerfiles) including 2.6 and 2.7 compat
- 🏗 Dockerfiles to create build/test environments
- ✅ run_tests.sh now exits on first failure, and returns exit code (for automation)
- ✅ BETA: Add a type testing comparator to assist with validating request/header bodies