Skip to content

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

6 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

@red-hat-developer-hub/lightspeed-playwright-e2e

Reusable Playwright helpers for Lightspeed: page objects, API route mocks, i18n strings, and bootstrapLightspeedE2ePage. Consume it from rhdh-plugins, rhdh-plugin-export-overlays, or any other repo—same idea as depending on a small shared npm package.

Install

Published on npm (after a maintainer runs npm publish; requires publish rights on the @red-hat-developer-hub scope):

npm install -D @red-hat-developer-hub/lightspeed-playwright-e2e@^0.1.0 @playwright/test

From GitHub until then — pin a tag or commit so installs stay reproducible (#main moves with every push):

npm install -D "github:redhat-developer/lightspeed-playwright-e2e#v0.1.0"
# or: github:redhat-developer/lightspeed-playwright-e2e#<commit-sha>

If no release tag exists yet, use #main or a full commit SHA until you tag.

The package entrypoint is compiled dist/ JavaScript (not raw src/ TypeScript). Installing from Git or npm runs the prepare script, which builds dist/ and copies upload fixtures. For a file: checkout, run npm run build once in this repo before your consumer resolves imports.

Local path (monorepo / sibling clone):

{
  "devDependencies": {
    "@red-hat-developer-hub/lightspeed-playwright-e2e": "file:../lightspeed-playwright-e2e"
  }
}

Use

import {
  bootstrapLightspeedE2ePage,
  openChatbot,
  models,
} from '@red-hat-developer-hub/lightspeed-playwright-e2e';

Your repo keeps only playwright.config.ts and *.spec.ts / *.test.ts files; mocks and page objects live here.

Publish

Source repo: redhat-developer/lightspeed-playwright-e2e. The package.json repository.url matches that origin.

To publish @red-hat-developer-hub/lightspeed-playwright-e2e to npm you need maintainer/publish access to the @red-hat-developer-hub org on npm. Until then, depend via github:redhat-developer/lightspeed-playwright-e2e#<tag-or-commit> (see Install).

  1. Bump version in package.json.
  2. Tag and push, e.g. git tag v0.1.0 && git push origin v0.1.0.
  3. npm publish (while logged in as an org member with publish rights).

Syncing from rhdh-plugins

Lightspeed UI strings live under src/i18n/ (copied from backstage-plugin-lightspeed). When plugin translations change, copy those files again or automate sync in CI.

License

Apache-2.0 (same as rhdh-plugins Lightspeed).

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors

Languages