cypress-example-kitchensink
Advanced tools
Readme
This is an example app used to showcase Cypress.io testing. The application uses every API command in Cypress for demonstration purposes. Additionally this example app is configured to run tests in various CI platforms. The tests are also heavily commented. For a full reference of our documentation, go to docs.cypress.io.
To see the kitchen sink application, visit example.cypress.io.
| CI | Build status | basic config file | full parallel config |
|---|---|---|---|
| AWS Amplify Console | amplify.yml | ||
| AWS CodeBuild | basic/buildspec.yml | buildspec.yml | |
| AppVeyor | appveyor.yml | ||
| Azure CI | basic/azure-ci.yml | azure-ci.yml | |
| Buddy | buddy.yml | ||
| Buildkite | .buildkite/pipeline.yml | ||
| Circle |  | basic/.circleci/config.yml | .circleci/config.yml |
| Codeship Pro | basic/codeship-pro | ||
| GitHub Actions |  | single.yml | parallel.yml |
| GitLab |  | basic/.gitlab-ci.yml | .gitlab-ci.yml |
| Heroku CI | basic/app.json | ||
| Jenkins | basic/Jenkinsfile | Jenkinsfile | |
| Netlify | netlify.toml | ||
| Semaphore v2 |  | basic/.semaphore.yml | .semaphore/semaphore.yml |
| Shippable | shippable.yml | ||
| Travis |  | basic/.travis.yml | .travis.yml |
You can find all CI results recorded on the 
If you are looking for BitBucket Pipelines example, check out bitbucket.org/cypress-io/cypress-example-kitchensink.
Cypress team has created a full workshop showing how to run Cypress on popular CI providers. Find the workshop at github.com/cypress-io/cypress-workshop-ci.
| CI | Url |
|---|---|
| IBM Cloud CI | Cloud Foundry |
| GitLab CI | Example caching when installing using Yarn |
| CodeFresh | bahmutov/cypress-codefresh-example |
If you get stuck, here is more help:
If you want to experiment with running this project in Continous Integration, you'll need to fork it first.
After forking this project in Github, run these commands:
## clone this repo to a local directory
git clone https://github.com/<your-username>/cypress-example-kitchensink.git
## cd into the cloned repo
cd cypress-example-kitchensink
## install the node_modules
npm install
## start the local webserver
npm start
The npm start script will spawn a webserver on port 8080 which hosts the Kitchen Sink App.
You can verify this by opening your browser and navigating to: http://localhost:8080
You should see the Kitchen Sink App up and running. We are now ready to run Cypress tests.
## launch the cypress test runner
npm run cy:open
shortcut: you can use command npm run local:open that uses start-server-and-test to start local server and open Cypress. When you close Cypress, the local server is stopped automatically. Similarly you can use npm run local:run to start the server, run Cypress tests headlessly and close the server.
Follow these instructions to install and write tests in Cypress.
Check out the Contributing Guideline.
FAQs
This is an example app used to showcase Cypress.io End-to-End (E2E) testing. For a full reference of our documentation, go to https://docs.cypress.io
The npm package cypress-example-kitchensink receives a total of 326 weekly downloads. As such, cypress-example-kitchensink popularity was classified as not popular.
We found that cypress-example-kitchensink demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Product
Socket now supports four distinct alert actions instead of the previous two, and alert triaging allows users to override the actions taken for all individual alerts.
Security News
Polyfill.io has been serving malware for months via its CDN, after the project's open source maintainer sold the service to a company based in China.
Security News
OpenSSF is warning open source maintainers to stay vigilant against reputation farming on GitHub, where users artificially inflate their status by manipulating interactions on closed issues and PRs.