0.17.2

Released Released on September 5, 2016

Notes:

  • After this update if you are seeing <iframe> origin errors please let us know by opening an issue. We will screen-share with you to diagnose the issue. We're no longer aware of any situation where this should happen, so if you're experiencing these bugs, please help us track them down.

Features:

  • Attempting to cy.visit() a non text/html resource will now throw a specific error message instead of bombing on page injection with an <iframe> origin error. You have to visit actual html, you cannot visit something like a .json or .png. If you're wanting to visit an API route on your back end that does something like set cookies (thus avoiding loading your UI) you can just use cy.request() for this since it will now automatically get and set cookies under the hood. Fixes #211.

Bugfixes:

  • Fixed a regression in 0.17.1 that was incorrectly setting Cache headers. This could cause a situation where you received an <iframe> origin error. Additionally we now set No-Cache headers whenever we inject content, but otherwise respect the headers coming from web servers. When using Cypress as the file server, we set etags but prevent caching.

  • Most likely fixed a bug that was crashing Cypress due to Cannot set headers after they've been sent. We were unable to write a test for this since we could not recreate the error, but analyzed how it may happen and fixed the code there. open an issue if you see this error, it will be obvious since Cypress will literally crash.

  • We stopped minifying vendor.js (for real this time). More optimizations to come around this.

  • Prevented accidentally setting domain cookies when they were really hostOnly cookies, thus duplicating the number of cookies sent on requests. Kudos to @bahmutov for finding this one. Fixes #207.

  • Fixed some edge cases in cypress-core-extension where it threw errors when attempting to executeScript on a tab with about:blank or chrome:// urls.

  • We've fixed some underlying issues with cy.go() during cypress run. It always worked fine in real Chrome. Previously there were some situations where it would not navigate forward / back correctly.

Misc: