#Frameio blog how to#

Let's confirm that the window.fetch method was called by the application with expected parameters. In this case, it is a JSON object representing a 'todo' resource with certain keys and values. We can inspect the response returned by the server by clicking on the request. When the user or Cypress clicks the 'Try it' button, the web application is making a fetch request to a REST API endpoint.

Custom command with a single log and an assertion Spying on window.fetch The Command Log in the left column looks much nicer now. Let's write the first test in spec file cypress/integration/first-spec.js that visits the page. Tip: we will be using data-cy attribute to find the iframe following our Best Practices for selecting elements guide. The new Camera to Cloud devices API enables you to embed the power of Frame.io in your hardware devices, extending the software tools and workflows that keep teams connected and working together. Let's take a static HTML page and embed an iframe. Frame.io customers and partners can use our REST APIs to create custom workflow solutions and app integrations. Note: you can find the source code for this blog post in the recipe 'Working with iframes' located in the repository cypress-example-recipes.

#Frameio blog how to#

In this blog post I will show how to interact with DOM elements inside an iframe (even if the iframe is served from another domain), how to spy on window.fetch requests that the iframe makes, and even how to stub XHR requests from the iframe. If your web application uses iframes, then working with elements in those iframes requires your own custom code. iframe when it sees a Cypress command (re-enactment) Mostly because all built-in cy DOM traversal commands do hard stop the moment they hit #document node inside the iframe.