cypress-localstorage-commands
cypress-ld-control
cypress-localstorage-commands | cypress-ld-control | |
---|---|---|
2 | 3 | |
178 | 17 | |
- | - | |
5.6 | 0.0 | |
5 months ago | over 1 year ago | |
JavaScript | JavaScript | |
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.
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.
cypress-ld-control
-
What are some best practices to turn on and off the feature flags through the automated test suite?
I wrote a blog post about it “ Control LaunchDarkly From Cypress Tests” https://glebbahmutov.com/blog/cypress-and-launchdarkly/
-
Effective Test Strategies for Deployed NodeJS Services using LaunchDarkly Feature Flags and Cypress. Part2: testing
My friend Gleb Bahmutov authored an excellent blog on testing LD with Cypress, there he revealed his new plugin cypress-ld-control. We used it in Effective Test Strategies for Front-end Applications using LaunchDarkly Feature Flags and Cypress. Part2: testing. The distinction here is using the plugin for a deployed service and the consequential test strategies.
-
Effective Test Strategies for Testing Front-end Applications using LaunchDarkly Feature Flags and Cypress. Part2: testing
The cypress-ld-control plugin utilizes cy.task, which allows node code to execute within Cypress context. Therefore we will not be able to use cypress.env.json to store these LD related environment variables locally.
What are some alternatives?
Cypress - Fast, easy and reliable testing for anything that runs in a browser.
github-action - GitHub Action for running Cypress end-to-end & component tests
cypress-image-snapshot - Catch visual regressions in Cypress
dotenv - Loads environment variables from .env for nodejs projects.
knapsack-pro-cypress - Knapsack Pro for Cypress.io test runner in JavaScript. It splits tests in dynamic way across parallel CI nodes to get faster CI build time.
cypress-crud-api-test - crud testing a serverless application with Cypress api tests
github-action-store-variable - Easily persist and read variables to reuse them between GitHub Action jobs
as-a - Runs a given command with additional environment settings for simple local development
cypress-grep - Filter tests using substring
pizza-api
cypress-fail-fast - A Cypress plugin to skip tests on first failure.
cy-spok - Playing with spok inside Cypress