knapsack-pro-cypress
cypress-localstorage-commands
knapsack-pro-cypress | cypress-localstorage-commands | |
---|---|---|
1 | 2 | |
42 | 178 | |
- | - | |
6.3 | 5.6 | |
11 months ago | 5 months ago | |
JavaScript | JavaScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
knapsack-pro-cypress
-
BitBucket parallel Cypress tests configuration for CI pipeline integration
image: cypress/base:10 options: max-time: 30 # job definition for running E2E tests in parallel with KnapsackPro.com e2e: &e2e name: Run E2E tests with @knapsack-pro/cypress caches: - node - cypress script: # run web application in the background - npm run start:ci & # env vars from https://support.atlassian.com/bitbucket-cloud/docs/variables-and-secrets/ - export KNAPSACK_PRO_CI_NODE_BUILD_ID=$BITBUCKET_BUILD_NUMBER - export KNAPSACK_PRO_COMMIT_HASH=$BITBUCKET_COMMIT - export KNAPSACK_PRO_BRANCH=$BITBUCKET_BRANCH - export KNAPSACK_PRO_CI_NODE_TOTAL=$BITBUCKET_PARALLEL_STEP - export KNAPSACK_PRO_CI_NODE_INDEX=$BITBUCKET_PARALLEL_STEP_COUNT # https://github.com/KnapsackPro/knapsack-pro-cypress#configuration-steps - export KNAPSACK_PRO_FIXED_QUEUE_SPLIT=true - $(npm bin)/knapsack-pro-cypress artifacts: # store any generated images and videos as artifacts - cypress/screenshots/** - cypress/videos/** pipelines: default: - step: name: Install dependencies caches: - npm - cypress - node script: - npm ci - parallel: # run N steps in parallel - step: <<: *e2e - step: <<: *e2e - step: <<: *e2e definitions: caches: npm: $HOME/.npm cypress: $HOME/.cache/Cypress
cypress-localstorage-commands
-
Effective Test Strategies for Testing Front-end Applications using LaunchDarkly Feature Flags and Cypress. Part2: testing
Cypress clears local storage between tests — it blocks — and LD sets a random user in local storage. This works great when a spec file has a single it block, but what happens when there are multiple it blocks? We can handle that with cypress-localstorage-commands as well.
-
How to preserve localStorage between Cypress tests
The cypress-localstorage-commands plugin allows you to use all browser localStorage methods through Cypress commands, and preserve it between tests. It also allows to simulate that localStorage is disabled in the browser.
What are some alternatives?
github-action - GitHub Action for running Cypress end-to-end & component tests
Cypress - Fast, easy and reliable testing for anything that runs in a browser.
google-forms-automation - JavaScript / Cypress script that fills out Google Forms automatically.
cypress-image-snapshot - Catch visual regressions in Cypress
cypress-and-jest - Cypress and Jest both with code coverage running unit tests
cypress-ld-control - Set LaunchDarkly feature flags from Cypress tests
starter-kit - Starter kit for full-stack JavaScript projects
github-action-store-variable - Easily persist and read variables to reuse them between GitHub Action jobs
cypress-example-recipes - Various recipes for testing common scenarios with Cypress
cypress-grep - Filter tests using substring
snapshot - Adds value / object / DOM element snapshot testing support to Cypress test runner
cypress-fail-fast - A Cypress plugin to skip tests on first failure.