All notable changes will be documented in this file.
postman-bdd
adheres to Semantic Versioning.
v5.0.0 (2017-06-11)
Upgraded to Chai.js 4.0, which includes some breaking changes. If these changes affect you, then you can continue using Postman BDD v4 by downloading it from the following URL (notice the v4
in the path):
http://bigstickcarpet.com/postman-bdd/dist/v4/postman-bdd.min.js
v4.3.0 (2017-04-08)
- Added TypeScript definitions (thanks to urosjarc for the pull request)
v4.2.1 (2017-03-07)
-
Ensure that all header names in the
response.headers
object are lowercased. This should have always been the case, since it's consistent with the SuperAgent API -
Minor tweak to the way
before
andafter
hooks are labeled. Previously, the label included the name of thedescribe
block that the hook ran before/after -
Refactored the
response
object to expose simple fields rather than property getters. This simplifies the code, and performs slightly better.
v4.0.0 (2017-03-06)
- Test names are now prefixed with a number to ensure uniqueness. Previously, if you have two tests with the same name, the first one wouldn't be recorded, since Postman uses a dictionary to store test results
-
Added a sample Postman collection with several requests that demonstrate basic and advanced usage of Postman BDD
-
Added a
response.should.be.xml
assertion, which is a shorthand for asserting that theContent-Type
header is set toapplication/xml
v3.0.0 (2017-03-05)
-
If the response is JSON or XML, then it is automatically parsed for you. No need to call
JSON.parse()
orxml2json()
first. -
If automatic body parsing fails (e.g invalid JSON or XML), then no error is thrown. Instead,
response.body
will just be the plain-text response
- Fixed issue #5, where a failed assertion would appear as multiple failed tests in Postman