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
Hello, I posted this question on SO a couple of days ago but no answers yet, and it looks like you have ended the google group. In my node/esm project testing with ava, nyc and sinon I'm not sure why my spy on console.log isn't noticing a log to the console.
Sinon version : 7.2.3
Environment : node 10.15.1, npm 6.5.0, windows 10
Other libraries you are using: esm 3.2.4, nyc 13.2.0, ava 1.2.1
What did you expect to happen?
In another part of my project I have successfully spied on console.log for call counts and args passed and here I expected the same - acknowledgement via callCount that a message was logged to the console.
What actually happens
callCount is 0 instead of 1, notCalled is true
Getting somewhere! The test passes when you comment out the import statement in main, so I guess this has something to do with esm so I will close this for now.
Hello, I posted this question on SO a couple of days ago but no answers yet, and it looks like you have ended the google group. In my node/esm project testing with ava, nyc and sinon I'm not sure why my spy on console.log isn't noticing a log to the console.
node
10.15.1,npm
6.5.0, windows 10esm
3.2.4,nyc
13.2.0,ava
1.2.1What did you expect to happen?
In another part of my project I have successfully spied on console.log for call counts and args passed and here I expected the same - acknowledgement via callCount that a message was logged to the console.
What actually happens
callCount is 0 instead of 1, notCalled is true
How to reproduce
test repo here
The text was updated successfully, but these errors were encountered: