cypress-example-recipes
cypress-example-recipes copied to clipboard
cypress-io
Various recipes for testing common scenarios with Cypress
When test-examples.js finds all recipes with `npm run test:ci` command or `npm run test:ci:chrome` it should print recipes WITHOUT it to warn users about new recipes that are not tested
- find all elements with inline styles (good to make sure there are none for more secure pages). use `*[style]` selector. - images that failed to load (use `naturalWidth` property)...
Also add this to the FAQ
Either as a pyramid of doom or using a helper function that flattens multiple actions ```js cy.get(...) .then(one => { cy.get(...) .then(two => { // compare one with two for...
Hanging in a build like https://ci.appveyor.com/project/cypress-io/cypress-test-example-repos/builds/27775485 Cypress v3.5.0 pre-release ``` ----------------------------------------- Testing examples/fundamentals__module-api ----------------------------------------- > [email protected] test:ci:windows C:\Users\appveyor\AppData\Local\Temp\1\cypress-example-recipeszL0JZI\examples\fundamentals__module-api > node ./e2e-tests ... Test run summary --------------------------------------- spec tests passes failures...
When using the following example: examples/fundamentals__fixtures/cypress/integration/require-fixtures-spec.js fixtures are located in subfolders, and therefore traversed up the folder tree, e.g.: require('../some-folder/some-file-here) Which works fine when running **the single test spec** -...
Related to this issue: https://github.com/cypress-io/cypress/issues/669
Such as dropdown, dialogs, etc. Also create a custom child command for programmatically interacting with JS api's directly to avoid using the DOM.
Metadata
Owner
Metadata
Various recipes for testing common scenarios with Cypress