v1.1.4: Merge pull request #29 from Financial-Times/allow-304

Allow 304 as an okay status

v1.1.3: Merge pull request #28 from Financial-Times/dont-mutate-req-headers

Don't mutate the request headers

v1.1.2: Merge pull request #27 from Financial-Times/add-response-header-check

• Add responseHeaders check
• [BUG] Fix request header setting

Allow booleans for networkRequest/element checks

Merge pull request #26 from Financial-Times/network-check-flexible

Allow booleans for network/element checks, and consolidate test fixtures

v1.1.0: Merge pull request #25 from Financial-Times/rework-api

• Now exports a class SmokeTest rather than an instance.
• Ability to programatically add new checks
• Removes --auth, and adds --header to add headers to every test.
• Adds networkRequests check, to be able to test that a URL has been requested.

v1.1.0-beta.3: Fix content type setting

 🐿 v2.6.0

v1.1.0-beta.1: Fix tests

• Allow consumers to add their own checks (as an example - FT.com could add a specific check to test cache headers).
• Remove FT-specific "auth" option. In place, when programatically using you can add global headers. This means in n-heroku-tools we can specify

This is technically a breaking change, but since it's only n-heroku-tools that would break, i'll do a beta release and sync.

Also adds a networkRequests check - to check that requests have been made to URLs. Example - check that tracking works, or an ad request was made.

v1.1.0-beta.2: Merge pull request #24 from Financial-Times/fix-html-check

Use lowercase headers from puppeteer

v1.0.2: Merge pull request #24 from Financial-Times/fix-html-check

Use lowercase headers from puppeteer

v1.0.1: Merge pull request #23 from Financial-Times/no-more-heroku

No more heroku