Skip to content

Bug: ng test --code-coverage doesn't display spec results in the browser in CLI rc2 #5513

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
johnpapa opened this issue Mar 20, 2017 · 3 comments
Labels
P5 The team acknowledges the request but does not plan to address it, it remains open for discussion

Comments

@johnpapa
Copy link
Contributor

OS

Mac OSX Sierra 10.12.3

Versions

@angular/cli: 1.0.0-rc.2
node: 6.9.1
os: darwin x64
@angular/common: 4.0.0-rc.5
@angular/compiler: 4.0.0-rc.5
@angular/core: 4.0.0-rc.5
@angular/forms: 4.0.0-rc.5
@angular/http: 4.0.0-rc.5
@angular/material: 2.0.0-beta.2
@angular/platform-browser: 4.0.0-rc.5
@angular/platform-browser-dynamic: 4.0.0-rc.5
@angular/router: 4.0.0-rc.5
@angular/cli: 1.0.0-rc.2
@angular/compiler-cli: 4.0.0-rc.5

Repro steps.

  • Install RC2
  • Run ng test --code-coverage

The browser opens and the spec list does not appear

  • Run ng test

The browser opens and the spec list does appear

  • Install RC1
  • Run ng test --code-coverage

The browser opens and the spec list does appear

In all cases, the spec execution results are shown correctly in the terminal.

It seems there was a regression from rc1 to rc2 on this

image

@delasteve
Copy link
Contributor

delasteve commented Mar 20, 2017

Should be fixed with #5514

Dupe of #5136

@filipesilva filipesilva added command: test P5 The team acknowledges the request but does not plan to address it, it remains open for discussion labels Mar 20, 2017
@filipesilva
Copy link
Contributor

Closing as dupe of #5136

@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
P5 The team acknowledges the request but does not plan to address it, it remains open for discussion
Projects
None yet
Development

No branches or pull requests

3 participants