Not passed test
See original GitHub issueNot passed test cli when supplied with report output file path should write the file and create dirs if they don't exist:
Tell us about your environment
- **ESLint Version: 3.12.2
- **Node Version: 7.2.0
- **npm Version: 3.10.9
**What parser (default, Babel-ESLint, etc.) are you using? Default
What did you do? Please include the actual source code causing the issue.
$ npm test
What did you expect to happen?
all passed tests
What actually happened? Please include the actual, raw output from ESLint.
13566 passing (1m)
1 failing
1) cli when supplied with report output file path should write the file and create dirs if they don't exist:
AssertionError: expected '\nC:\\Users\\ivdemidov\\AppData\\Local\\Temp\\eslint\\fixtures\\single-quoted.js\n 1:13 warning Strings must use doublequote quotes\n\n✖ 1 problem (0 errors, 1 warning)\n' to include 'C:\\Users\\IVDEMI~1\\AppData\\Local\\Temp\\eslint\\fixtures\\single-quoted.js'
at Function.assert.include (D:\sand-box\git\eslint\node_modules\chai\lib\chai\interface\assert.js:843:45)
at Context.it (D:\sand-box\git\eslint\tests\lib\cli.js:541:20)
at callFn (D:\sand-box\git\eslint\node_modules\mocha\lib\runnable.js:326:21)
at Test.Runnable.run (D:\sand-box\git\eslint\node_modules\mocha\lib\runnable.js:319:7)
at Runner.runTest (D:\sand-box\git\eslint\node_modules\mocha\lib\runner.js:422:10)
at D:\sand-box\git\eslint\node_modules\mocha\lib\runner.js:528:12
at next (D:\sand-box\git\eslint\node_modules\mocha\lib\runner.js:342:14)
at D:\sand-box\git\eslint\node_modules\mocha\lib\runner.js:352:7
at next (D:\sand-box\git\eslint\node_modules\mocha\lib\runner.js:284:14)
at Immediate.<anonymous> (D:\sand-box\git\eslint\node_modules\mocha\lib\runner.js:320:5)
=============================================================================
Writing coverage object [D:\sand-box\git\eslint\coverage\coverage.json]
Writing coverage reports at [D:\sand-box\git\eslint\coverage]
=============================================================================
=============================== Coverage summary ===============================
Statements : 99.48% ( 11563/11624 ), 147 ignored
Branches : 98.2% ( 8891/9054 ), 75 ignored
Functions : 99.9% ( 1999/2001 ), 22 ignored
Lines : 99.47% ( 11490/11551 )
================================================================================
START:
20 12 2016 16:17:43.628:WARN [karma]: Port 9876 in use
20 12 2016 16:17:43.631:INFO [karma]: Karma v0.13.22 server started at http://localhost:9877/
20 12 2016 16:17:43.636:INFO [launcher]: Starting browser PhantomJS
20 12 2016 16:17:45.261:INFO [PhantomJS 2.1.1 (Windows 8 0.0.0)]: Connected on socket ep7LPmVfCAehOM8-AAAA with id 88475412
Finished in 0.644 secs / 0.589 secs
SUMMARY:
√ 233 tests completed
npm ERR! Test failed. See above for more details.
Issue Analytics
- State:
- Created 7 years ago
- Comments:12 (12 by maintainers)
Top Results From Across the Web
grammaticality - Is it correct to say "testing passed / failed"?
It's common to say "Testing passed" or "testing failed". I don't think anyone would question this. It's not a complete, ...
Read more >3 Critical Steps If You Fail Your Driver's License Test
The main thing is to try to find out why you did not pass either the permit test or the actual driver's road...
Read more >Is it better to say “I did not pass” instead of “I failed” because ...
It is similar to “I wish I had been there.” 2. "I wish I could have passed the test" is also a present...
Read more >Test execution basics: passed, failed, crashed - Kotlin Testing
When the test passes, when it fails and why it crashes? In this short note we will try to ... Test will pass,...
Read more >6 Reasons Why Not Passing Your Driving Test First Time Isn't ...
There's a lot of pressure on young drivers to pass the daunting practical test first time. It's something I didn't achieve, in my...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Does the issue still occur if you change this line to use
path.resolve.apply
instead ofpath.join.apply
?It seems to be fixed if I remove
require("mock-fs")
fromtests/lib/config.js
.