If you'd like to contribute directly to the Cypress code, we'd love to have your
The Cypress code is open source and licensed under anĪre a few tips on getting started that we've outlined below. If you want to dive into Cypress and edit the code yourself, you can do that. This plugin writes the list of Cypress commands to the terminal as wellĪs a JSON file if a test fails. For example,Īdditional information Write command log to the terminal You can combine several areas together using the comma character. Git commit and CI information when recording to the Cypress Dashboard Running the plugins file and bundling specs The top-level command line parsing problems Here are a few common log sources and when you might Server, reporter, driver, command line, etc. This allows you to isolate the problem a little better Log sourcesĬypress is built from multiple packages, each responsible for its own logging: # prints messages only from config parsing DEBUG =cypress:server:config. # prints ALL messages from server package DEBUG =cypress:server*. # prints very few top-level messages DEBUG =cypress:server. If you cannot open Cypress, search your file system for aĭirectory named cy whose content should look something like this: This will take you to the directory in your file system where your App Data.You may fixĪn issue you have by clearing this app data.
Sometimes this data can become corrupted.
You can see the full list of found browsers and their properties within theĪnother way to log what is found by Cypress is to run Cypress with theĭEBUG environment variable set to cypress:launcher. See 'Launching Browsers' for more information You can also supply the -browser command line argument to launch a browserįrom a known filesystem path to bypass browser auto detection. This will clear out all installed versions of Cypress that may be cached on your
If you're having an issue during installation of Cypress, try removing the Specific released version of Chrome (dev, Canary and stable) for every platform. Sometimes causing a breaking change in your automated tests.
The Chrome browser is evergreen - meaning it will automatically update itself, Run the same tests in both Electron andĬhrome, then compare the screenshots/videos. The problem might be isolated to the Electron browser. Split large spec files into smaller ones.When debugging a failing test, follow these general principles to isolate the LabelĬypress cannot be downloaded or installed Suggest a workaround or shed more information on the problem. Maybe you canįind an open or closed issue matching your problem. Issue(s) and links to the open and closed issues in the topic. Support, which gives you one-on-one help from our team.īelow are some of common problem topics users experience with a link to the main If your organization signs up for one of our.Search this documentation (search is in the top right) ?.In this situation, we recommend checking these support resources There are times when you will encounter errors or unexpected behavior withĬypress itself.