@spscommerce/e2e-core 2.4.9 → 2.4.10
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/Dockerfile +1 -1
- package/README.md +5 -0
- package/package.json +1 -1
package/Dockerfile
CHANGED
package/README.md
CHANGED
|
@@ -125,6 +125,11 @@ 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.
|
|
128
133
|
|
|
129
134
|
## Run tests in CI (Azure Pipelines)
|
|
130
135
|
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.
|