Releases: cypress-io/cypress
Releases · cypress-io/cypress
0.6.11
0.6.10
Released 06/06/2015
Bugfixes:
- Improved clicking algorithm to reduce edge cases where element could not be clicked but should have been able to be clicked.
Misc:
- .click() accepts
{force: true}
which will force it to issue the click event and bypass checking to ensure element is physically clickable. - Elements which are children of a container with
overflow
are automatically scrolled prior to a click (which is an abstraction around real user behavior). - Elements that are covering up an element you targeted for .click() are now logged out in the command console.
- All elements are now logged out as real DOM elements instead of jQuery wrapped elements. This has several upsides. Chrome will allow you to immediately interact with these elements, drilling into their contents, displaying the element box model on hover, etc. This prevents you from having to expand the jQuery elements and click "Reveal in Elements Panel".
0.6.9
0.6.8
Released 06/05/2015
Features:
- cy.clearCookie() and cy.clearCookies() have been added as new commands.
- Cypress will automatically clear all cookies before each test run.
- Named the spec + app iframe so that inside of Chrome Dev Tools the iframe selector will clearly distinguish which iframe is your application versus Cypress.
Bugfixes:
- Hitbox is no longer covered up by element layers on DOM revert.
- Finally tracked down and fixed edge case causing empty view to display when tests were not empty. Fixes #13
Misc:
- cy.visit() now accepts
{log: false}
to prevent logging out (useful in custom commands). - cy.contains() is now scoped by default to the
<body>
instead ofdocument
which prevents it from returning elements in thehead
liketitle
.
0.6.7
Released 06/04/2015
Features:
- When reverting the DOM, associated command elements are now automatically scrolled into view.
- Hitboxes are now displayed on the screen based on the actual coordinates where an
action command
event took place. - Click events now display event information about the
mousedown
/mouseup
/click
default action + propagation in the command console. - Preventing default action on
mousedown
will no longer give focus as per the spec. - Click events are now issued in the exact center of an element (taking into account 2d transforms) and provide the coordinates in the command console and in the actual event
- Click events now take into account whether the associated element is being covered up by another element, and will retry or fail with an exact error message if the click was unable to be issued due to this reason.
- Click events will now intelligently provide
focus
to the first focusable element on the stack at the click coordinates, or will givefocus
to the window. - Click events will issue the click to the topmost element based on the click coordinates and not necessarily to the element you requested to e clicked (which simulates exactly how a real click works). If this happens it is noted in the command console and provides the
Actual Element Clicked
.
Bugfixes:
- When hover over commands element layers (2d transforms like rotation) are now taken into account and displayed correctly.
- There was a bug when checking / unchecking
:checkbox
where it did not properly receive focus.
Misc:
- Click events are now replicated almost identically to the W3C click spec. They should behave for all intents and purposes, identically to real clicks in the browser.
0.6.6
Released 05/31/2015
Bugfixes:
- Fixed regression related to cy.visit() not re-visiting when current match matches remote url.
0.6.5
Released 05/23/2015
Features:
- When Cypress detects a regular HTTP page loading event (where we're leaving the current page and requesting a new one) it will now insert a
loading
command which indicates to the user Cypress has stopped running commands until the new page loads. - If for some reason this new page errors Cypress will display the initial 500 error messages just like cy.visit().
- Cypress now waits
20s
(which matches cy.visit()) for the new page to load instead of4s
previously.
Bugfixes:
- .submit() will actually submit the form for real now, instead of just firing the submit event. Now it's been upgraded to be able to be cancelled or have its returnValue set to false and will not submit the form. Don't ask how I missed this one. I as once a young naive programmer who trusted the DOM not to be the abomination it actually is.
Misc:
- No longer send back a 500 message when initial response status code is 4xx.
0.6.4
0.5.15
Released 05/07/2015
Bugfixes:
- Reverted
window.location
overrides. This broke things in unexpected ways and after further testing would not have worked onFirefox
andIE
. It's back to the drawing board (but I have some ideas). Apps usingpushState
routing are broken again.
0.5.14
Released 05/06/2015
Features:
- Cypress now works with JS applications that use
pushState
andreplaceState
routing (commonly known asHTML5 History
) without having to change any application code. - Cypress now always updates the remote URL whenever your application changes its URL through the vast variety of ways it can do this.
Bugfixes:
- Removed
iframe
andlink[rel=stylesheet]
elements during DOM revert. - Server instrument now correctly displays the number of responses their corresponding routes have had.
- Spies/Stubs/Mocks instrument now correctly displays the number of calls their corresponding methods have had.
- When users navigate between pages with commands, like .click(), Cypress now correctly waits until the age has finished loading before running more commands. Previously this waited for the
unload
event, which did not fire synchronously, and ow we bind tobeforeunload
which does. Additionally Cypress checks to ensurebeforeunload
did not return a non-undefined value.
Misc:
- More changes to prepare for server adapters,