You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My repository uses Enzyme and Jasmine to test our code. I'm migrating it over to using React-testing-library. The way I have it set up, is that both the enzyme tests and the RTL tests run from the same test command.
I mention that because prior to this migration, wallaby worked correctly. However, after the migration, when I do an exclusive test run, the Output Inspector only ever displays
"There are currently no output fragments, Shift + Esc to close the window
Output fragments are removed when you use debug actions"
If I perform an exclusive test run, and one of the tests fails, and I try to "Show error details", it opens the Output Inspector with the above message. The inline messaging in the test file displays the details about the failure. And if I set the Output view in VSCode to "Wallaby.js Tests", it seems to display the correct details from the failure. However, if I open the Output view to "Wallaby.js Console", it displays the following error message. Do you have any thoughts on what might be causing this error?
[Error] Failed to start addInspections operation, TypeError: _0x15cdd7[_0x2758(...)] is not a function
[Error] at _0x1dba5b (/Users/iepstein/.vscode/extensions/wallabyjs.wallaby-vscode-1.0.334/wallabyb30bb2/node_modules/ws/lib/Sender.fallbacks.js:1:532692)
[Error] at _0x4c829f.(anonymous function).(anonymous function) [as _emitInspections] (/Users/iepstein/.vscode/extensions/wallabyjs.wallaby-vscode-1.0.334/wallabyb30bb2/node_modules/ws/lib/Sender.fallbacks.js:1:535594)
[Error] at _0x4c829f.(anonymous function).(anonymous function) [as addInspections] (/Users/iepstein/.vscode/extensions/wallabyjs.wallaby-vscode-1.0.334/wallabyb30bb2/node_modules/ws/lib/Sender.fallbacks.js:1:461831)
[Error] at _0x566442.(anonymous function).(anonymous function) [as addInspections] (/Users/iepstein/.vscode/extensions/wallabyjs.wallaby-vscode-1.0.334/wallabyb30bb2/node_modules/ws/lib/Sender.fallbacks.js:1:172166)
[Error] at Object.i.receive (/Users/iepstein/.vscode/extensions/wallabyjs.wallaby-vscode-1.0.334/wallabyb30bb2/server.js:14:21942)
[Error] at WebSocket.<anonymous> (/Users/iepstein/.vscode/extensions/wallabyjs.wallaby-vscode-1.0.334/wallabyb30bb2/server.js:30:18103)
[Error] at WebSocket.emit (events.js:198:13)
[Error] at WebSocket.EventEmitter.emit (domain.js:448:20)
[Error] at Receiver.ontext (/Users/iepstein/.vscode/extensions/wallabyjs.wallaby-vscode-1.0.334/wallabyb30bb2/node_modules/ws/lib/WebSocket.js:841:10)
[Error] at /Users/iepstein/.vscode/extensions/wallabyjs.wallaby-vscode-1.0.334/wallabyb30bb2/node_modules/ws/lib/Receiver.js:536:18
[Error] at /Users/iepstein/.vscode/extensions/wallabyjs.wallaby-vscode-1.0.334/wallabyb30bb2/node_modules/ws/lib/Receiver.js:368:7
[Error] at /Users/iepstein/.vscode/extensions/wallabyjs.wallaby-vscode-1.0.334/wallabyb30bb2/node_modules/ws/lib/PerMessageDeflate.js:249:5
[Error] at afterWrite (_stream_writable.js:485:3)
[Error] at onwrite (_stream_writable.js:476:7)
[Error] at InflateRaw.afterTransform (_stream_transform.js:94:3)
[Error] at Zlib.processCallback (zlib.js:557:8)
Issue description or question
My repository uses Enzyme and Jasmine to test our code. I'm migrating it over to using React-testing-library. The way I have it set up, is that both the enzyme tests and the RTL tests run from the same test command.
I mention that because prior to this migration, wallaby worked correctly. However, after the migration, when I do an exclusive test run, the Output Inspector only ever displays
If I perform an exclusive test run, and one of the tests fails, and I try to "Show error details", it opens the Output Inspector with the above message. The inline messaging in the test file displays the details about the failure. And if I set the Output view in VSCode to "Wallaby.js Tests", it seems to display the correct details from the failure. However, if I open the Output view to "Wallaby.js Console", it displays the following error message. Do you have any thoughts on what might be causing this error?
Wallaby diagnostics report
The text was updated successfully, but these errors were encountered: