Closed sean-roberts closed 7 years ago
ah, weird. Has something to do with having the db adaptor linked locally.
Not too familiar with this problem. But it seems that because it's a linked project the file-db is not in the require path that jest is going to mock, thus it's still going to use the actual functions.
Not sure that there is a way to fix this that's very elegant...
how is your env set up to run npm test? I keep getting lots of flak for async/await @mxstbr
Yeah testing changes in the adapter is a bit of a pain right now, I'm afraid...
master tests are failing - also the ci build tag isn't reflecting this correctly