@spscommerce/e2e-core 2.4.9 → 2.4.11

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/.dockerignore CHANGED
@@ -1,8 +1,8 @@
1
1
  # Ignore all files by default
2
2
  *
3
3
  # White list the required files
4
- !helpers/
5
- !package-lock.json
4
+ !.yarnrc.yml
6
5
  !package.json
6
+ !playwright.config.js
7
7
  !tsconfig.json
8
- !playwright.config.ts
8
+ !yarn.lock
package/.yarnrc.yml ADDED
@@ -0,0 +1 @@
1
+ nodeLinker: node-modules
package/Dockerfile CHANGED
@@ -1,10 +1,11 @@
1
- FROM mcr.microsoft.com/playwright:v1.46.0-noble
1
+ FROM mcr.microsoft.com/playwright:v1.46.1-noble
2
2
 
3
3
  ARG BROWSER
4
4
 
5
5
  RUN mkdir e2e
6
6
  WORKDIR /e2e
7
7
  COPY . .
8
+ RUN corepack enable && corepack prepare yarn@4.4.0 --activate
8
9
  RUN yarn
9
10
  RUN if [ "$BROWSER" = "edge" ]; then npx playwright install msedge; fi
10
11
  RUN if [ "$BROWSER" = "chrome" ]; then npx playwright install chrome; fi
package/README.md CHANGED
@@ -125,6 +125,18 @@ RUN if [ "$BROWSER" = "chrome" ]; then npx playwright install chrome; fi
125
125
  ```
126
126
  > Attention:
127
127
  > Installed Playwright package version must match the Docker image version.
128
+ > You can find exact version here: https://mcr.microsoft.com/en-us/product/playwright/tags
129
+
130
+ ## Publish package
131
+ If you want to publish your package to the npm registry and have changed any files from `src` folder, you must build the package first. Run the following command: `yarn build`.
132
+ After that, push changed files from the `lib` and `src` folders to your PR. You need to follow the [pattern](https://gist.github.com/joshbuchea/6f47e86d2510bce28f8e7f42ae84c716) of the semantic commit messages (should begin from __fix:__ or __feat:__), like:
133
+ ```
134
+ fix: Update Dockerfile to restore build process
135
+ ```
136
+ or
137
+ ```
138
+ feat: Bump @playwright/test package to the last version
139
+ ```
128
140
 
129
141
  ## Run tests in CI (Azure Pipelines)
130
142
  In order to add an Azure Pipeline for your framework, head over to https://dev.azure.com/spscommerce/ and find your team. You can create a new pipeline by selecting your Git repository. For more information on getting started with Azure, visit https://github.com/SPSCommerce/azure-pipelines-config.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@spscommerce/e2e-core",
3
- "version": "2.4.9",
3
+ "version": "2.4.11",
4
4
  "description": "An automation test framework which is based on Playwright.",
5
5
  "main": "./lib/index.js",
6
6
  "types": "./lib/index.d.ts",
@@ -26,12 +26,13 @@
26
26
  "license": "UNLICENSED",
27
27
  "dependencies": {
28
28
  "@playwright/test": "1.46.1",
29
- "@typescript-eslint/eslint-plugin": "5.30.0",
30
- "@typescript-eslint/parser": "5.30.0",
31
- "dotenv": "16.0.3",
32
- "eslint": "7.32.0",
29
+ "@typescript-eslint/eslint-plugin": "6.21.0",
30
+ "@typescript-eslint/parser": "6.21.0",
31
+ "dotenv": "16.4.5",
32
+ "eslint": "8.20.0",
33
33
  "jest-expect-message": "1.0.4",
34
34
  "jest-extended": "1.2.0",
35
35
  "typescript": "4.7.4"
36
- }
36
+ },
37
+ "packageManager": "yarn@4.4.0+sha512.91d93b445d9284e7ed52931369bc89a663414e5582d00eea45c67ddc459a2582919eece27c412d6ffd1bd0793ff35399381cb229326b961798ce4f4cc60ddfdb"
37
38
  }