Support Forum
Search found 58 matches
Thanks for the responses!
I have the following questions open: 1. Watch mode Is there a watch mode where the tests will be automatically re-executed during development? Eg: if a source or test file changes on the disk. Something like karma's watch mode. 2. Comparison to jasmine test-cases I didn't dig deep into this, but wha...
The bug is still there, but it happens hitting Page-down then Page-up now.
Regarding the non-working `--nyc.include` on windows - seems one just need to use double quotes for this config. Some specifics of windows terminal. Works fine for me after this, can you confirm? I'll add a note in coverage guide as well. Yes, I can confirm that with double quotes, it works on wind...
Hm.. I can see its Windows, probably also need to convert the path separators to '\' I'll try. I'll run it on linux too to see what happens. Feedback: On linux I have some positives!! bin/webdriver local/examples/sencha-extjs/index-no-ui.html --headless --debug --include code_coverage --nyc.reporte...
Tried it also without port: bin\webdriver local/examples/sencha-extjs/index-no-ui.html --headless --debug --include code_coverage --nyc.reporter=text --nyc.include='**/*code_coverage*/*.js' The proxy notice is there: [DEBUG] PROXYING request for https://local/examples/sencha-extjs/5.code_coverage/01...
Ok, the localhost proxy did something. I don't seem to get the --nyc.include working properly, it's not matching anything... With --nyc.all I get some coverage report (haven't checked it yet in detail) Screenshot_361.png See the 2 results below, log files are attached. d:\Temp\siesta-5.2.2-trial>bin...
I am not blocked by this. As I wrote I am running an evaluation. My current target is to understand how the code coverage works and for that I would need to see the results. But it's not blocking anything unless you tell me we'll find a solution in 2 months :) I'll give it a shot with another host n...