Can`t make breakpoints using debugger in unit test about angular-starter

[darxx]

Tomorrow I will try to run separately. I hope this helps.

[antonybudianto7]

Anyway I need more details on how you do the debugging.
For now, I just tried gulp test -w and used Karma Chrome launcher, then clicked DEBUG button on launcher popup, and then I started to put debugger; statement in spec file, and refresh the debug page, here is what I got

It worked well (although I got tslint warning on debugger; usage, well it's okay since you only debug it)

I can even log the scopes

[antonybudianto7]

because ts files are not loaded directly via script tag
https://karma-runner.github.io/0.13/config/files.html

[antonybudianto]

not sure how to fix this, this may help

[darxx]

This information was not very helpful. I guess this problems is related to type script remapping .

[antonybudianto7]

Remapping is a separate process after karma's done, not sure why it's the problem. I think the sourcemap is not properly loaded.

[darxx]

This works as expected. Working on "real time" debugging and compiling.
Created
gulpfile.js
gulp.task('serv', function() {
runSequence('serve-local', 'unit-test');
});

and
serve.js
gulp.task('serve-local', function ()
{
startBrowsersync(config.browserSync.dev);
});

Then added debugger after launched
gulp serv --exclude-source -w

I guess ['tsc-app', 'watch-ts'] need to be added.

[antonybudianto7]

closing this issue then, thanks

[darxx]

{ included: false, watched: false, pattern: 'src/app/*/.ts' },
In Karma why included: false is false?

[darxx]

After changing spec file need to kill gulp test -w and run over again.

[antonybudianto7]

Please explain the detail more, why you need to kill the test watch?
Working well on my side.

[darxx]

Can You Explain local development cycle writing code, test and checking changes on web server? Because every time I need to close gulp commands and start others tasks to preprocess type script and code coverage and start static server.

[darxx]

And using --exclude-source on every gulp command to avoid writing directly to c drive is not best solution. Currently local workflow is main issue.

[antonybudianto7]

If the problem is workflow, then it'll get nowhere, since everyone have different opinions on this. You can fork the starter and start implementing your desired flows, I'll help where I can.