You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
build: remove legacy integration test runner (angular#35985)
* integration tests target definitions in integration/BUILD.bazel updated to use a single dict
* payload tracking for integration tests updated to work under Bazel
* legacy integration_test CI job removed
* integration/run_tests.sh script no longer used in CI so it has been updated for running integration tests locally in the legacy way
PR Closeangular#35985
Copy file name to clipboardExpand all lines: integration/README.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -98,7 +98,7 @@ yarn bazel test //integration:bazel-schematics_test
98
98
99
99
When adding a new integration test, follow the steps below to add a bazel test target for the new test.
100
100
101
-
1. Add new test to `INTEGRATION_TESTS` object in `/integration/BUILD.bazel` (and tag as `"no-ivy-aot"` if not meant to be run against ivy bundles).*NB: if the test requires any special attribute then make a new angular_integration_test target instead.*
101
+
1. Add new test to `INTEGRATION_TESTS` object in `/integration/BUILD.bazel` (and tag as `"no-ivy-aot"` if not meant to be run against ivy bundles).
102
102
2. If test requires ports and does not support ethereal ports then make sure the port is unique and add it to the "manually configured ports" comment to document which port it is using
103
103
3. Add at least the following two entries `.bazelignore` (as they may contain BUILD files)
0 commit comments