72c36956de
By default, `webdriver-manager update` will download the latest ChromeDriver version, which might not be compatible with the Chrome version included in the [docker image used on CI], causing CI failures. Previously, we used to pin the ChromeDriver version on CI in [ngcontainer's Dockerfile][2]. This was accidentally broken in #26691, while moving from ngcontainer to default CircleCI docker images. This commit fixes the issue by pinning ChromeDriver to a known compatible version. [1]: |
||
|---|---|---|
| .. | ||
| e2e | ||
| src | ||
| README.md | ||
| build.sh | ||
| package.json | ||
| tsconfig.json | ||
| webpack.client.config.js | ||
| webpack.server.config.js | ||
| yarn.lock | ||
README.md
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