Angular-cli: ng e2e should support --progress=false (or --no-progress)

Created on 29 Jun 2018  路  3Comments  路  Source: angular/angular-cli

Bug Report or Feature Request (mark with an x)

- [ ] bug report -> please search issues before submitting
- [x] feature request

Area

- [x] devkit
- [ ] schematics

Versions

Angular CLI: 6.0.8
Node: 8.9.4
OS: darwin x64
Angular: 6.0.3
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.6.8
@angular-devkit/build-angular     0.6.8
@angular-devkit/build-optimizer   0.6.8
@angular-devkit/core              0.6.8
@angular-devkit/schematics        0.6.8
@angular/cli                      6.0.8
@ngtools/webpack                  6.0.8
@schematics/angular               0.6.8
@schematics/update                0.6.8
rxjs                              6.2.0
typescript                        2.7.2
webpack                           4.8.3

Repro steps

ng e2e --no-progress

The log given by the failure

Unknown option: '--progress'

Desired functionality

I'd prefer to be able to turn of progress logging for continuous integration builds.

devkibuild-angular faq feature

Most helpful comment

There is no progress logging in e2e tests per se. The progress reporting comes from the dev server target. With some very limited exceptions, we don't want to add "pass-through" options as that limits what options a given builder can use.

You can add a configuration to your dev server that turns off progress, and then use that one in the e2e target, then call it via ng e2e --configuration=ci.

        "serve": {
          "builder": "@angular-devkit/build-angular:dev-server",
          "options": {
            "browserTarget": "latest-project:build"
          },
          "configurations": {
            "ci": {
              "progress": false
            }
          }
        },
// ...
        "e2e": {
          "builder": "@angular-devkit/build-angular:protractor",
          "options": {
            "protractorConfig": "e2e/protractor.conf.js"
          },
          "configurations": {
            "ci": {
              "devServerTarget": "latest-project:serve:ci"
            }
          }
        },

All 3 comments

There is no progress logging in e2e tests per se. The progress reporting comes from the dev server target. With some very limited exceptions, we don't want to add "pass-through" options as that limits what options a given builder can use.

You can add a configuration to your dev server that turns off progress, and then use that one in the e2e target, then call it via ng e2e --configuration=ci.

        "serve": {
          "builder": "@angular-devkit/build-angular:dev-server",
          "options": {
            "browserTarget": "latest-project:build"
          },
          "configurations": {
            "ci": {
              "progress": false
            }
          }
        },
// ...
        "e2e": {
          "builder": "@angular-devkit/build-angular:protractor",
          "options": {
            "protractorConfig": "e2e/protractor.conf.js"
          },
          "configurations": {
            "ci": {
              "devServerTarget": "latest-project:serve:ci"
            }
          }
        },

Would be good to update the story on the wiki with above comment's suggestion.

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_This action has been performed automatically by a bot._

Was this page helpful?
0 / 5 - 0 ratings