angular/integration/platform-server
Paul Gschwendtner 2664bc2b3e test: switch integration tests from puppeteer/webdriver-manager to Bazel-managed chromium (#44238)
Switches the integration tests form Puppeteer/webdriver-manager to the
Bazel-managed Chromium/Chromedriver. This is now possible with the new
integration test rule for which we can consult the
`dev-infra/bazel/browsers` toolchain and setup environment variables.
This has been configured already in a previous commit.

This commit also includes some additional small cleanups necessary for
the new integration test rule:

* The `test.sh` scripts have been renamed as they would conflict with
  the `test.sh` scripts generated by the integration test rule.
  Previously this was not an issue because tests were declared at a
  higher-level. As mentioned though this has other downsides and it is
  trivial to rename the file.

* Related to the point above, since tests are now declared witin the
  actual test folder (for perf e.g.), `package.json` files setting
  `"type": "module"` will accidentally cause the `nodejs_test`-generated
  files to be considered ESM. This is not correct and likely needs to be
  fixed upstream in `rules_nodejs` where explicit `.cjs` extensions
  should be used. This is only happening **once** in the `injectable-def`
  test so it is acceptable doing that for now.

PR Close #44238
2021-12-08 13:42:42 -05:00
..
e2e test: switch integration tests from puppeteer/webdriver-manager to Bazel-managed chromium (#44238) 2021-12-08 13:42:42 -05:00
src test: run platform-server integration test with v13 partial compilation packages (#43431) 2021-10-01 18:28:44 +00:00
base-config.mjs test: re-enable platform-server integration test (#44055) 2021-11-04 18:57:22 +00:00
BUILD.bazel build: setup test targets for integration tests with new rule (#44238) 2021-12-08 13:42:41 -05:00
build.sh test: run platform-server integration test with v13 partial compilation packages (#43431) 2021-10-01 18:28:44 +00:00
package.json test: switch integration tests from puppeteer/webdriver-manager to Bazel-managed chromium (#44238) 2021-12-08 13:42:42 -05:00
README.md test: move platform-server integration test (#22810) 2018-04-13 16:30:50 -07:00
tsconfig.json test: run platform-server integration test with v13 partial compilation packages (#43431) 2021-10-01 18:28:44 +00:00
webpack.client.config.mjs test: run platform-server integration test with v13 partial compilation packages (#43431) 2021-10-01 18:28:44 +00:00
webpack.server.config.mjs test: run platform-server integration test with v13 partial compilation packages (#43431) 2021-10-01 18:28:44 +00:00
yarn.lock test: switch integration tests from puppeteer/webdriver-manager to Bazel-managed chromium (#44238) 2021-12-08 13:42:42 -05:00

To add a new server side rendering E2E test

  • Add a new server side rendered application to src/
  • Edit webpack.client.config.js to add new entry point for the new client bundle
  • The index.html can access the client bundle from /built/.js
  • Edit src/server.ts to add the server side application to a new URL
  • Add a protractor test in e2e/ to test with the new URL