search

nvim-neotest / neotest-jest

MIT License
118 stars 79 forks source link

Summary Status is "skipped" although "assertionResult.status" is "passed" #35

Closed jmeischner closed 11 months ago

jmeischner commented 2 years ago

Dear haydenmeade,

thank you for making this plugin 🙏. Unfortunately I have an issue with the status report in neotests summary window. I always get the status skipped although the test results output file is stating something different. CleanShot 2022-08-29 at 00 28 29@2x CleanShot 2022-08-29 at 00 19 44@2x

I get this behavior for different project setups (nx Monorepo & default Next.js application repo). I also added a log output here: https://github.com/haydenmeade/neotest-jest/blob/408245bec62813ed858de49ca07172d3f018a79f/lua/neotest-jest/init.lua#L248 which prints a passed status, so it seems the correct result is going through that procedure. I have no idea what leads to that behavior. I am even not sure if it's a neotest-jest or a neotest issue 🙈

Could you provide some guidance?

Thank you, Jan

codejunkienick commented 1 year ago

I think I had the same issue. What helped for me is changing 

require "neotest-jest" {
                jestCommand = "yarn test --",

to 

require "neotest-jest" {
                jestCommand = "yarn test",
jmeischner commented 1 year ago

Trank you @codejunkienick

For me this issue magically disappeared in the meantime, most likely because I updated nvim and this plugin recently 🤷‍♂️ but im not completely sure what I've done to fix it, because I haven't tried it for some time 🧙‍♀️🙈