mirror of
https://github.com/digital-asset/daml.git
synced 2024-09-20 01:07:18 +03:00
37ca4af529
This PR gets yarn test running the Puppeteer end-to-end tests in the GSG integration test. The first step of the test is adding the extra dependencies (Jest, Puppeteer and more). The GSG recommends a yarn add command, but this does not work against HEAD. This is because yarn add does not use resolutions in the parent package.json, and then complains about unknown versions 0.0.0 of the daml TS libaries. The solution here is to hack in the extra dependencies into the ui/package.json and then yarn install. This works, but it hard codes version numbers which we would need to maintain. I would like to be able to say version "latest", which is what yarn add would install. The next step of the test is to copy the index.test.ts file and run yarn test in CI mode. I've moved the GSG test to a new create-daml-app-tests target. It's marked "exclusive" in Bazel until we figure out how to avoid hardcoding port numbers. This is a bit tricky since the HTTP port is hardcoded in a couple of places in ui/package.json. Finally, this PR gets the GSG testing docs to reference the code in the new templates/create-daml-app-test-resources folder. changelog_begin changelog_end |
||
|---|---|---|
| .. | ||
| daml-helper | ||
| daml-project-config/DA/Daml/Project | ||
| daml-sdk | ||
| exe/DA/Daml | ||
| integration-tests | ||
| scala-daml-project-config | ||
| src/DA/Daml/Assistant | ||
| test/DA/Daml/Assistant | ||
| BUILD.bazel | ||
| daml-project-config.cabal | ||
| get-daml.sh | ||