Skip to content

Testing Workflow #38

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
aaweb opened this issue Apr 8, 2016 · 1 comment
Closed

Testing Workflow #38

aaweb opened this issue Apr 8, 2016 · 1 comment

Comments

@aaweb
Copy link

aaweb commented Apr 8, 2016

Hey Nathan

Just a quick question about what the intended workflow is for testing or test-driven development. Currently, I'm using the debug commands:

# Debug - In two different shell windows
npm run build.test.watch      # 1st window
npm run karma.start           # 2nd window

However, even when using iit or ddescribe to only run certain tests, the delay from save to the tests actually passing takes at least 30 seconds.

Is this workflow only meant for debugging or what is the intended usage here? Glad to hear your insight.

Andy

@NathanWalker
Copy link
Owner

Hi @aaweb, that is the current TDD workflow at the moment.
If you'd like to see improvements to that or have any suggestions, you might post an issue on the parent angular2-seed here. All build tooling at the moment derives directly from that parent seed for consistency.

This discussion brings up some related issues: mgechev/angular-seed#645

Once we can move to rxjs beta 3/4 and above, things should improve with regards to that.
Thanks for the question and feel free to post additional thoughts (just going to close this issue for now).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants