npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@trustpayments/js-payments-card

v2.2.603

Published

TypeScript Payment Card

Downloads

734

Readme

JS Payment Card

Repository:

You can check JS Library in action by running it on your local environment. To do this, run commands below:

npm install
npm start

Then open address https://localhost:8443 in your web browser.

Technology Stack:

Tools and languages:
QA:
  • Jest for unit testing

Browser compatibility:

  • Internet Explorer 10 or later
  • Latest versions of the following:
    • Chrome
    • Firefox
    • Edge
    • Safari

Testing how-to

Selenium tests are stored in tests\selenium directory and all the below actions are to be executed in that directory.

Application docker

Tests will required the docker in order to execute them.

Application docker will be pulled from gitlab's container registry

The address to an appropiate image is stored in .env file and can be edited.

Start up the docker containers

docker-compose up -d

The example page is available under address https://merchant.securetrading.net/. You should add this domain to your hosts file and point to address 127.0.0.1 (here you can find how to do it https://support.rackspace.com/how-to/modify-your-hosts-file/).

The Wiremock is available under https://webservices.securetrading.net:8443/ so to access it you should also add this address to the hosts file.

To run the tests

docker-compose run tests poetry run behave features

To test a different branch

If you have multiple application images with different branches you can specify which image should be used for tests, eg.:

APP_TAG=master docker-compose up -d

To run with a remote browser via browserstack:

In directory binary execute BrowserStackLocal.exe --key <BROWSERSTACK_ACCESS_KEY> --local-identifier local_id --force-local

Then, to run docker-compose run -e LOCAL=true -e REMOTE=true -e BROWSER=Chrome -e BROWSER_VERSION=80.0 -e OS=Windows -e OS_VERSION=10 -e BS_USERNAME=<BROWSERSTACK_USERNAME> -e BS_ACCESS_KEY=<BROWSERSTACK_ACCESS_KEY> tests poetry run behave features

License