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 🙏

© 2026 – Pkg Stats / Ryan Hefner

kalliope-e2e

v3.1.0

Published

For end to end testing of XDATA deployment

Readme

kalliope-e2e

For end to end testing of XDATA deployment

Structure POM

  📦kalliope-e2e
  ┣ 📂.github
  ┃ ┗ 📂workflows
  ┃ ┃ ┣ 📜ci.yml
  ┃ ┃ ┗ 📜playwright.yml
  ┣ 📂Data
  ┃ ┗ 📜user.js
  ┣ 📂node_modules
  ┣ 📂pages
  ┃ ┣ 📜home.page.js
  ┃ ┣ 📜login.page.js
  ┃ ┗ 📜register.page.js
  ┣ 📂playwright-report
  ┃ ┗ 📜index.html
  ┣ 📂test-results
  ┃ ┗ 📜.last-run.json
  ┣ 📂tests
  ┃ ┣ 📜example.spec.js
  ┃ ┣ 📜home.spec.js
  ┃ ┣ 📜login.spec.js
  ┃ ┗ 📜register.spec.js
  ┣ 📂tests-examples
  ┃ ┗ 📜demo-todo-app.spec.js
  ┣ 📂utils
  ┃ ┗ 📜common.js
  ┣ 📜.gitignore
  ┣ 📜README.md
  ┣ 📜package-lock.json
  ┣ 📜package.json
  ┗ 📜playwright.config.js

Here’s a brief description of each folder:

  • .github/workflows: This folder will contains CI setup.
  • Data/: This folder contains the test data require for testing.
  • node_modules/: This folder contains the function support from playwright.
  • pages/: This folder will contain the page objects for our application. Each page object will have methods and properties that represent the page’s elements and actions.
  • playwright-report/: This folder will contain the reports generated by our tests.
  • test-results/: This folder will contain the result after execute.
  • tests/: This folder will contain the test files for our application. Each test file will use the page objects to perform the tests.
  • tests-examples/: This folder will contain the sample script to help you check environment ready or not.
  • untils/: This folder will contain the common function.

Setup environment

Nodejs

On remote coder for insall Nodejs you need to run: sudo yum install nodejs

Install

Run npm init playwright@latest and select option javascript and another option is true

Script Execute

npx playwright test: Runs the end-to-end tests.

npx playwright test <name>: Run with specific test

npx playwright test --ui: Starts the interactive UI mode.

npx playwright test --project=chromium: Runs the tests only on Desktop Chrome.

npx playwright test example: Runs the tests in a specific file.

npx playwright test --debug: Runs the tests in debug mode.

npx playwright codegen: Auto generate tests with Codegen.

npx playwright show-report: To open last HTML report run

Note with case you want to debug, codegen and run with ui open. You cannot open on headed browser