Files
cypress/packages/desktop-gui
Zach Bloomquist b6703aaec7 Add support for sameSite in cookie-related commands (#6828)
* add experimental feature for sameSite

* allow experimental descriptions to render markdown

* sameSite support mostly working

* also strip sameSite from setCookie yielded value

* don't use `unspecified` - let browser set default

* add tests

* decaffeinate: Rename cdp_automation_spec.coffee from .coffee to .js

* decaffeinate: Convert cdp_automation_spec.coffee to JS

* decaffeinate: Run post-processing cleanups on cdp_automation_spec.coffee

* cleanup cdp_automation_spec.ts

* update unit tests

* update settings_spec to not render as markdown

* user-friendly error for insecure SameSite=None

* fix styling

* fix markdown renderer

* update types + schema

* use renderInline

* update experiment summary

* bind renderFn to md
2020-03-27 10:04:50 -04:00
..
2020-01-27 23:10:26 +06:30

Desktop GUI

The Desktop GUI is the react application that is rendered by Electron. This acts as the visual user interface you see when running: cypress open.

screen shot 2017-12-07 at 11 13 45 am

The Desktop GUI has the following responsibilities:

  • Allow users to log in through GitHub.
  • Allow users to add projects to be tested in Cypress.
  • Display existing projects and allow the removal of projects.
  • Initialize the server to run on a specific project.
  • Allow users to choose a specific browser to run tests within.
  • Display the resolved configuration of a running project.
  • Display the list of specs of a running project.
  • Initialize the run of a specific spec file or all spec files chosen by the user.
  • Notify users of updates to Cypress and initialize update process.
  • Set up projects to be recorded.

Building

For development

## from repo root
yarn build --scope @packages/desktop-gui

For production

## from repo root
yarn build-prod --scope @packages/desktop-gui

Developing

NOTE: Currently, if you want to work on the code around logging in, viewing runs, or setting up new projects to record, this requires connecting to a locally running API server.

Our API server is only accessible to Cypress employees at the moment. If you want to work with the code, we recommend working within the Cypress tests for the Desktop-Gui. There are lots of tests mocking our API server around logging in, seeing runs, and setting up projects.

Watching

This watches and compiles all changes as you make them.

  • Runs *.js and *.jsx through babel and bundles with browserify into dist
  • Compiles *.scss files into dist
## from repo root
yarn watch --scope @packages/desktop-gui

Running

You can also run all of the Desktop GUI's tests locally. We don't really recommend this because it takes a long time, and we have this process optimized by load balancing the tests across multiple workers in CI.

It's usually easier to run the tests in the GUI, commit, and then see if anything broke elsewhere.

First, start local http server

## from repo root
yarn lerna run start --scope @packages/desktop-gui

Then run Cypress with

## from repo root
yarn lerna run cypress:run --scope @packages/desktop-gui --stream

Testing

In Cypress

This project is tested with Cypress itself. It acts exactly like any other Cypress project.

First, start local http server

## from repo root
yarn lerna run start --scope @packages/desktop-gui

Then open Cypress with

## from repo root
yarn lerna run cypress:open --scope @packages/desktop-gui --stream