angular/tools/testing
Paul Gschwendtner 985dbdb511 build: remove unnecessary import to @bazel/jasmine (#48521)
Since we no properly initialize as part of the spec-entrypoint
the hacky logic starting Jasmine can be removed. The init
file now runs before tests run, but after Jasmine is initialized.

Calling `boot` while Jasmine is already initialized results in
tests executing in a different context and before other
initialization work completes.

PR Close #48521
2022-12-19 19:50:41 +00:00
..
browser_tests.init.ts build: update jasmine_node_test macro to support ESM (#48521) 2022-12-19 19:50:41 +00:00
BUILD.bazel build: ensure bootstrap transitive runfiles are made available (#48521) 2022-12-19 19:50:41 +00:00
fail.spec.js build: update license headers to reference Google LLC (#37205) 2020-05-26 14:26:58 -04:00
node_no_angular_tests.init.ts build: update jasmine_node_test macro to support ESM (#48521) 2022-12-19 19:50:41 +00:00
node_tests.init.ts build: remove unnecessary import to @bazel/jasmine (#48521) 2022-12-19 19:50:41 +00:00
README.md feat(ivy): first steps towards ngtsc mode (#23455) 2018-04-25 13:25:33 -07:00

The spec helper files here set up the global testing environment prior to the execution of specs.

There are 3 options:

  • init_node_spec - configures a node environment to test Angular applications with platform-server.
  • init_node_no_angular_spec - configures a node environment for testing without setting up Angular's testbed (no dependency on Angular packages is incurred).
  • init_browser_spec - configures a browser environment to test Angular applications.