Skip to content

Releases: cypress-io/cypress

0.11.6

19 Jul 07:28
Compare
Choose a tag to compare

Released 09/25/2015

Bugfixes:

  • Viewport is now properly restored to the default width / height after on subsequent runs. Previously it would retain the last viewport sized sed until there was a new viewport command.
  • cy.should('contain', '...') now correctly escapes quotes and single quotes.
  • Assertion messages are no longer truncated, and instead will scale down by reducing the font-size and line-height after they exceed 110 characters. So you'll now always see the full assertion message.
  • Fixed some scenarios where assertions would not be logged as a child command.
  • Assertions based around the window or document object no longer cause chai to bomb on formatting their object structures (due to yclic references) and instead now will show up as <window> and <document>.

Misc:

  • cy.window() now logs out to the Command Log and additionally verifies upcoming assertions.
  • cy.document() now logs out to the Command Log and additionally verifies upcoming assertions.
  • Removed numElements label on assertions which indicated the number of elements found if > 1. This was annoying and redundant since the inked command already had this number.

0.11.5

19 Jul 07:28
Compare
Choose a tag to compare

Released 09/20/2015

Features:

  • The Linux version of Cypress now works correctly for GUI Desktop versions (tested on Ubuntu Desktop). Previously it would only worked during cypress run in server versions. The tray used in OSX does not work with the Linux, so in Linux we just use a standard window + menu.
  • Added Desktop Icon.

Bugfixes:

  • Cypress now forces the initial cy.visit() not to be cached by the browser. This was incorrectly being ached which meant when you changed the cy.visit() it would not actually go out and fetch the new contents. reviously you had to check Disable Cache in the Network Tab inside of Chrome to prevent this bug. Unfortunately this has a significant erformance drawback. If you use a cy.visit() before each test you will notice a degrade in performance ecause this request is no longer cached. This is a temporary problem until Cypress implements a more sophisticated caching strategy which ptimizes these concerns. There is a lot to improve in this arena but it will take more time before it's implemented.
  • .should() will no longer throw an error when it is used as a parent command and has a callback unction signature, and that callback function throws outside of an assertion. Instead now it logs correctly, handles the error, and displays his error for you.

Misc:

  • Many additional tests added to the multi-os deployment process.
  • When Cypress opens other windows they are now auto-focused.

0.11.4

19 Jul 07:28
Compare
Choose a tag to compare

Released 09/17/2015

Features:

  • .should() now accepts a callback function which will be retried until it does not throw. The callback unction will be retried in the exact same way as passing regular string-based chainers to .should(). aving a callback function gives you an opportunity to massage the expected subject such as comparing multiple elements, creating an array of ext or classes, etc.

Deprecations:

  • cy.wait(function) has been deprecated and you can safely rename this command to .should().

Misc:

0.11.3

19 Jul 07:28
Compare
Choose a tag to compare

Released 09/16/2015

Features:

  • When XHR's are aborted Cypress will display the stack trace indicating where in your app the XHR was aborted. Additionally it will display s (aborted) in the command log.

Bugfixes:

  • XHR's will no longer be ended early and display no status as if there was no response. Fixes #63.
  • XHR's which are aborted no longer cause an INVALID_STATE_ERR to be thrown. Fixes #62 and #34.
  • Cypress will no longer incorrectly revert to a previous test run's snapshot when tests are re-run.

0.11.2

19 Jul 07:28
Compare
Choose a tag to compare

Released 09/14/2015

Bugfixes:

  • Prevented bug where the assertion message: expected <x> element to exist would log over and over again when Cypress retried querying for a OM element.

Misc:

  • .root() now outputs its subject when clicking on its command log. Fixes #55.

0.10.8

19 Jul 07:27
Compare
Choose a tag to compare

Released 08/21/2015

Features:

  • Reporters in CI can now be specified.
  • Added teamcity reporter.

0.10.7

19 Jul 07:27
Compare
Choose a tag to compare

Released 08/16/2015

Features:

  • Port can now be specified as a CLI argument and will override any values stored in cypress.json.

Misc:

  • When running through the CLI, Cypress will now display an error if the server's port is currently in use. Previously this would not output an rror and the process would just hang.

0.10.6

19 Jul 07:27
Compare
Choose a tag to compare

Released 08/15/2015

Bugfixes:

  • Fixed edge case where Cypress would not correctly handle POST or PUT requests with a JSON body. These requests would just hang and ventually time out.

Misc:

  • Project ID's can be programmatically set now.

0.10.5

19 Jul 07:27
Compare
Choose a tag to compare

Released 08/13/2015

Bugfixes:

  • Running a specific test won't open/close immediately when starting up (fixes weird flickering effect).
  • .check() and .uncheck() commands will now correctly "end" even if they were noop due to the element already being in a checked or unchecked state.

Misc:

  • Currently running tests now display a spinner to indicate they are currently running.
  • Optimized performance of command lists.
  • Commands which were silenced with {log: false} will now always display in the Command Log if they were part of a replayed chain of commands ue to an alias reference becoming stale. Previously they would not display which was very confusing.
  • sinon.js is no longer minified.

0.10.4

19 Jul 07:27
Compare
Choose a tag to compare

Released 08/11/2015

Bugfixes:

  • The OSX Cypress App was not being properly signed (since 0.10.0) due to an oversight in our deployment process. This has been fixed now and dditional checks have been added to ensure the deploy'd version is properly signed. Updating within the app was unaffected. This bug only ffected fresh downloads from the internet.
  • Errors / crashes encountered when updating to newer versions through the app should be fixed now.