chore: Add playwright e2e tests for example app #4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces end-to-end (E2E) testing using Playwright to the project. It includes updates to configuration files, new dependencies, and several new test cases.
E2E Testing Setup and Configuration:
.github/workflows/test.yaml
to run Playwright tests.package.json
to include Playwright and related dependencies. [1] [2]playwright.config.ts
to run tests on multiple browsers and set up a local dev server.Code and Configuration Changes:
.vscode/extensions.json
to recommend the Playwright extension for VS Code..eslintrc.json
to extend Playwright's recommended ESLint configuration and added specific rules for E2E test files. [1] [2]nx.json
to include the Playwright plugin configuration.New E2E Test Cases:
apps/ng-remote-config-example/e2e/app.spec.ts
,apps/ng-remote-config-example/e2e/config-asset.spec.ts
, andapps/ng-remote-config-example/e2e/features-asset.spec.ts
to validate the application’s functionality, including checking browser tab titles, JSON viewers, and verifying config files. [1] [2] [3]