npmpackage.info

Gathering detailed insights and metrics for cypress-plugin-stripe-elements

cypress-plugin-stripe-elements

A small Cypress plugin that assists you in filling in Stripe Elements inputs

1.0.2

MIT

JavaScript

5,660,924 2.6

Installations

npm install cypress-plugin-stripe-elements

Pull Requests

Open

2

Total

8

Closed

2

Merged

4

Issues

Open

5

Total

11

Closed

6

Releases

1.0.2

v1.0.2

Published on 07 Jul 2021

1.0.1

v1.0.1

Published on 17 Apr 2021

1.0.0 release

1.0.0

Published on 26 Dec 2020

View all 3 releases

Developer

dbalatero

Developer Guide

BETA

Module System

CommonJS

Min. Node Version

Typescript Support

Yes

Node Version

10.16.0

NPM Version

6.9.0 Statistics

37 Stars

38 Commits

5 Forks

3 Watching

2 Branches

3 Contributors

Updated on 02 Jul 2024

Languages

JavaScript (67.65%)

TypeScript (32.35%)

Total Downloads

Cumulative downloads

Total Downloads

5,660,924

Last day

-16.3%

6,526

Compared to previous day

Last week

-5.3%

37,260

Compared to previous week

Last month

-12%

163,861

Compared to previous month

Last year

21.2%

2,052,699

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dev Dependencies

cypress express start-server-and-test typescript

Versions

cypress-plugin-stripe-elements

Github Stars

This plugin provides a fillElementsInput that makes it easy to fill out Stripe Elements inputs without cy.wait() hacks or anything else.

1cy.fillElementsInput('cardNumber', '4242424242424242');

Installation

npm install --save-dev cypress-plugin-stripe-elements
# or
yarn add --dev cypress-plugin-stripe-elements

Set { "chromeWebSecurity": false } in your cypress.json file, or the plugin will not work.

Import the plugin in your cypress/support/index.js file:

1// cypress/support/index.js
2
3import 'cypress-plugin-stripe-elements';

TypeScript

Make sure to include the following types in your tsconfig.json file:

1{
2  "compilerOptions": {
3    "types": ["cypress", "cypress-plugin-stripe-elements"]
4  }
5}

Usage

This package provides a cy.fillElementsInput(name, value) command.

The name parameter can be one of:

cardNumber - credit card number field
cardExpiry - credit card MM/YY expiry field
cardCvc - credit card 3-digit CVC field
postalCode - postal/ZIP code

or any string value matching the data-elements-stable-field-name attribute of the Elements <input> you want to target. Use the DevTools/inspector to figure out the stable field name.

The value is whatever string you want to fill the field with.

1describe('payment form', () => {
2  it('allows for a successful payment', () => {
3    cy.visit(`http://localhost:4000`);
4
5    // It's recommended to scope `fillElementsInput` to a specific container
6    // in case you have multiple Stripe Elements on the page.
7    cy.get('#card-element').within(() => {
8      cy.fillElementsInput('cardNumber', '4242424242424242');
9      cy.fillElementsInput('cardExpiry', '1025'); // MMYY
10      cy.fillElementsInput('cardCvc', '123');
11      cy.fillElementsInput('postalCode', '90210');
12    });
13
14    // Click your Pay button (yours is different)
15    // cy.get('#pay-button').click();
16
17    // TODO: Assert some success state
18  })
19})

Development

To modify this plugin, git clone the repo and run yarn install. You can run the tests with yarn test after setting the environment variables CYPRESS_TEST_APP_PORT and STRIPE_PUBLISHABLE_KEY:

CYPRESS_TEST_APP_PORT=4000 STRIPE_PUBLISHABLE_KEY=your_key_here yarn test

Examples

[Local Demo from this repository](https://github.com/dbalatero/cypress-plugin-stripe-elements/blob/master/cypress/integration/basic_spec.ts
Stripe Payments Demo - stripe official demo project

No vulnerabilities found.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

License

Determines if the project has defined a license.

1

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

Maintained

Determines if the project is "actively maintained".

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

0

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Security-Policy

Determines if the project has published a security policy.

0

Fuzzing

Determines if the project uses fuzzing.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

SAST

Determines if the project uses static code analysis.

0

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

Score

2.6

/10

Last Scanned on 2024-11-25

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More