Skip to content
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

feat(command): ng test #70

Closed
cironunes opened this issue Nov 26, 2015 · 2 comments · Fixed by #86
Closed

feat(command): ng test #70

cironunes opened this issue Nov 26, 2015 · 2 comments · Fixed by #86
Assignees
Labels
feature Issue that requests a new feature

Comments

@cironunes
Copy link
Member

Create the ng test command to use karma start.

Maybe take the opportunity to abstract some configurations and let the karma-test-shim.js lighter.

@cironunes cironunes added the feature Issue that requests a new feature label Nov 27, 2015
Brocco added a commit to Brocco/angular-cli that referenced this issue Dec 2, 2015
Overrode the ember-cli test command to initialize the karma server
Then start the karma server based upon the karma.conf.js config file

closes angular#70
@Brocco
Copy link
Contributor

Brocco commented Dec 2, 2015

I just pushed a branch which is launching karma via ng test but am not thrilled with the Promise implementation. Not ready for a PR yet, just looking for some feedback...

Brocco added a commit to Brocco/angular-cli that referenced this issue Dec 3, 2015
Overrode the ember-cli test command to initialize the karma server
Then start the karma server based upon the karma.conf.js config file

closes angular#70
Brocco added a commit to Brocco/angular-cli that referenced this issue Dec 3, 2015
Overrode the ember-cli test command to initialize the karma server
Then start the karma server based upon the karma.conf.js config file

closes angular#70
Brocco added a commit to Brocco/angular-cli that referenced this issue Dec 5, 2015
Overrode the ember-cli test command to initialize the karma server
Then start the karma server based upon the karma.conf.js config file

closes angular#70
Brocco added a commit to Brocco/angular-cli that referenced this issue Dec 10, 2015
Overrode the ember-cli test command to initialize the karma server
Then start the karma server based upon the karma.conf.js config file

closes angular#70
Brocco added a commit to Brocco/angular-cli that referenced this issue Dec 10, 2015
Overrode the ember-cli test command to initialize the karma server
Then start the karma server based upon the karma.conf.js config file

closes angular#70
Brocco added a commit to Brocco/angular-cli that referenced this issue Jan 24, 2016
Overrode the ember-cli test command to initialize the karma server
Then start the karma server based upon the karma.conf.js config file

closes angular#70
Brocco added a commit to Brocco/angular-cli that referenced this issue Jan 24, 2016
Overrode the ember-cli test command to initialize the karma server
Then start the karma server based upon the karma.conf.js config file

closes angular#70
Brocco added a commit to Brocco/angular-cli that referenced this issue Jan 29, 2016
Overrode the ember-cli test command to initialize the karma server
Then start the karma server based upon the karma.conf.js config file

closes angular#70
Brocco added a commit to Brocco/angular-cli that referenced this issue Jan 30, 2016
Overrode the ember-cli test command to initialize the karma server
Then start the karma server based upon the karma.conf.js config file

closes angular#70
Brocco added a commit to Brocco/angular-cli that referenced this issue Jan 31, 2016
Overrode the ember-cli test command to initialize the karma server
Then start the karma server based upon the karma.conf.js config file

closes angular#70
Brocco added a commit to Brocco/angular-cli that referenced this issue Feb 3, 2016
Overrode the ember-cli test command to initialize the karma server
Then start the karma server based upon the karma.conf.js config file

closes angular#70
Brocco added a commit to Brocco/angular-cli that referenced this issue Feb 4, 2016
Overrode the ember-cli test command to initialize the karma server
Then start the karma server based upon the karma.conf.js config file

closes angular#70
Brocco added a commit to Brocco/angular-cli that referenced this issue Feb 4, 2016
Overrode the ember-cli test command to initialize the karma server
Then start the karma server based upon the karma.conf.js config file

closes angular#70
Brocco added a commit to Brocco/angular-cli that referenced this issue Feb 4, 2016
Overrode the ember-cli test command to initialize the karma server
Then start the karma server based upon the karma.conf.js config file

closes angular#70
@Brocco Brocco mentioned this issue Feb 5, 2016
Brocco added a commit to Brocco/angular-cli that referenced this issue Feb 5, 2016
Overrode the ember-cli test command to initialize the karma server
Then start the karma server based upon the karma.conf.js config file

closes angular#70
Brocco added a commit to Brocco/angular-cli that referenced this issue Feb 6, 2016
Overrode the ember-cli test command to initialize the karma server
Then start the karma server based upon the karma.conf.js config file

closes angular#70
Brocco added a commit to Brocco/angular-cli that referenced this issue Feb 6, 2016
Overrode the ember-cli test command to initialize the karma server
Then start the karma server based upon the karma.conf.js config file

closes angular#70
Brocco added a commit to Brocco/angular-cli that referenced this issue Feb 12, 2016
Overrode the ember-cli test command to initialize the karma server
Then start the karma server based upon the karma.conf.js config file

closes angular#70
Brocco added a commit to Brocco/angular-cli that referenced this issue Feb 12, 2016
Overrode the ember-cli test command to initialize the karma server
Then start the karma server based upon the karma.conf.js config file

closes angular#70
Brocco added a commit to Brocco/angular-cli that referenced this issue Feb 13, 2016
Overrode the ember-cli test command to initialize the karma server
Then start the karma server based upon the karma.conf.js config file

closes angular#70
Brocco added a commit to Brocco/angular-cli that referenced this issue Feb 13, 2016
Overrode the ember-cli test command to initialize the karma server
Then start the karma server based upon the karma.conf.js config file

closes angular#70
Brocco added a commit to Brocco/angular-cli that referenced this issue Feb 14, 2016
Overrode the ember-cli test command to initialize the karma server
Then start the karma server based upon the karma.conf.js config file

closes angular#70
Brocco added a commit to Brocco/angular-cli that referenced this issue Feb 14, 2016
Overrode the ember-cli test command to initialize the karma server
Then start the karma server based upon the karma.conf.js config file

closes angular#70
@Brocco Brocco self-assigned this Feb 14, 2016
Brocco added a commit to Brocco/angular-cli that referenced this issue Feb 14, 2016
Overrode the ember-cli test command to initialize the karma server
Then start the karma server based upon the karma.conf.js config file

closes angular#70
Brocco added a commit to Brocco/angular-cli that referenced this issue Feb 14, 2016
Overrode the ember-cli test command to initialize the karma server
Then start the karma server based upon the karma.conf.js config file

closes angular#70
@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 5, 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
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants