Skip to content

Feature request: Jasmine SpecRunner #2853

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
rcomblen opened this issue Oct 24, 2016 · 3 comments
Closed

Feature request: Jasmine SpecRunner #2853

rcomblen opened this issue Oct 24, 2016 · 3 comments
Labels
feature Issue that requests a new feature P5 The team acknowledges the request but does not plan to address it, it remains open for discussion

Comments

@rcomblen
Copy link

Would be great to be able to run unit tests using the Jasmine SpecRunner served by ng serve, rather than being forced to use Karma in development.

Karma is great for continuous integration and code coverage reporting, but not so nice for doing test driven development.

I've been using it with Angular 1 + Gulp + Livereload + SpecRunner.html and it was really great for productivity.

With Karma, I miss the ability to run a single test, and to have a easy view on the failed expectations (and I need to have two processes compiling my sources, ng serve and ng test.

Any chance to get that in a future release ?

@filipesilva filipesilva added feature Issue that requests a new feature P5 The team acknowledges the request but does not plan to address it, it remains open for discussion labels Oct 27, 2016
@leozulfiu
Copy link

The console can sometimes produce a big output, which is hard to use in development because of finding the beginning of a stacktrace for example. The specrunner has the ability to show me instantly which tests have failed.

@filipesilva
Copy link
Contributor

This isn't something we're looking at adding per se. We currently only support Karma, which needs a custom build setup as well. Adding another test option would be very time consuming relatively little benefit I believe.

@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 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature Issue that requests a new feature 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