angular-cn/aio/content/examples/component-interaction/example-config.json

{
  "tests": [
    {
      "cmd": "yarn",
      "args": [
        "e2e",
        "--protractor-config=e2e/protractor-puppeteer.conf.js",
        "--no-webdriver-update",
        "--port={PORT}"
      ]
    }
  ]
}
docs: run component-interaction and DI in JiT mode (#28592) PR Close #28592 2019-02-07 17:38:06 +00:00			`{`
build(docs-infra): renamed `e2e` property of `example-config.json` to `tests` (#36143) Each docs example has an `example-config.json` configuration file. Among other things, this file can be used to specify what commands to run in order to test the example. (If not specified, the `run-example-e2e.js` script will run a default `yarn e2e` command.) Previously, the property specifying the test commands was called `e2e`. This is because in the past only e2e tests were run for docs examples. Since recently, some examples may specify commands for other types of tests (such as unit tests). Therefore, calling the property that holds the list of test commands `e2e` no longer makes sense and can be misleading to people looking at the configuration files. This commit renamed the property to the more generic `tests`. In the future, the `run-example-e2e.js` script (and corresponding npm script) should be renamed and refactored to also avoid giving the impression that only e2e tests are run. Discussed in: https://github.com/angular/angular/pull/36143#discussion_r395148379 PR Close #36143 2020-03-23 17:31:56 +02:00			`"tests": [`
docs: run component-interaction and DI in JiT mode (#28592) PR Close #28592 2019-02-07 17:38:06 +00:00			`{`
			`"cmd": "yarn",`
			`"args": [`
			`"e2e",`
build(docs-infra): use `puppeteer` to get a browser for docs examples tests (#35381) In #35049, integration and AIO tests were changed to use the browser provided by `puppeteer` in tests. This commit switches the docs examples tests to use the same setup. IMPLEMENTATION NOTE: The examples are used to create ZIP archives that docs users can download to experiment with. Since we want the downloaded projects to resemble an `@angular/cli` generated project, we do not want to affect the project's Protractor configuration in order to use `puppeteer`. To achieve this, a second Protractor configuration is created (which is ignored when creating the ZIP archives) that extends the original one and passes the approperiate arguments to use the browser provided by `puppeteer`. This new configuration (`protractor-puppeteer.conf.js`) is used when running the docs examples tests (on CI or locally during development). PR Close #35381 2020-02-13 16:58:04 +02:00			`"--protractor-config=e2e/protractor-puppeteer.conf.js",`
build(docs-infra): support running cli docs examples concurrently (#29103) PR Close #29103 2019-03-04 20:33:25 +01:00			`"--no-webdriver-update",`
			`"--port={PORT}"`
docs: run component-interaction and DI in JiT mode (#28592) PR Close #28592 2019-02-07 17:38:06 +00:00			`]`
			`}`
			`]`
build(docs-infra): use `puppeteer` to get a browser for docs examples tests (#35381) In #35049, integration and AIO tests were changed to use the browser provided by `puppeteer` in tests. This commit switches the docs examples tests to use the same setup. IMPLEMENTATION NOTE: The examples are used to create ZIP archives that docs users can download to experiment with. Since we want the downloaded projects to resemble an `@angular/cli` generated project, we do not want to affect the project's Protractor configuration in order to use `puppeteer`. To achieve this, a second Protractor configuration is created (which is ignored when creating the ZIP archives) that extends the original one and passes the approperiate arguments to use the browser provided by `puppeteer`. This new configuration (`protractor-puppeteer.conf.js`) is used when running the docs examples tests (on CI or locally during development). PR Close #35381 2020-02-13 16:58:04 +02:00			`}`