The DEBUG=cypress:* logs don't seem to be here. Could you pipe them to a file and then upload them?

DEBUG=cypress:* yarn cypress run > logs.txt

it's done. I am still troubleshooting, based on the source code of cypress:

cy.task('coverageReport', null, {
      timeout: dayjs.duration(3, 'minutes').asMilliseconds(), // I thought that this is the issue here
      log: false
    }).then((coverageReportFolder) => {
      logInstance.set('consoleProps', () => ({
        'coverage report folder': coverageReportFolder
      }))
      logInstance.end()
      return coverageReportFolder
    })

Alright. I was worrying it was related to the size of the code you're trying to cover or the bundler setup (babel, etc)

@User , then I did start cypress with the debug, and I noticed:

cypress:server:task run task coverageReport with arg null +105ms
  cypress:server:plugins plugin event registered? { event: 'task', isRegistered: true } +4s
  cypress:server:plugins execute plugin event 'task' Node 'v14.15.1' with args: 'coverageReport' null undefined +1ms

So I would suggest creating a minimal example on Github and if it's reproducible there, it'll be easier for us to debug if it's an issue within Cypress.

That's fine. That's normal.

That just means cy.task was received by the Cypress server.

@User Yes, but it says the coverage report is

null

which apparently is from http://localhost:4200/__coverage__

Yeah, so i don't think istanbul is configured

So my assumption here is that it times out when it keeps getting

null

for a certain period (which is actually

null

)

Is that right?

I'm not sure. Gleb wrote that plugin and I haven't looked at it deeply. Seemingly I should.

one second.

Hello! We haven't looked at making Vite x Code Coverage work yet 😦

Ok, let me please ask you few questions, you could maybe help me think this better.

Yes please, go for it.

Do you have a GH repo with a reproduction? I can debug it there if you have something for me.

It's likely not even your application code. It's probably just your build tools and dependencies, so I'd likely take my repo, delete most of the code inside of it except for the build tooling, and some minimal code and a single test

Unfortunately not, as it's a huge project. But you can try to instrument https://github.com/Angular-RU/universal-starter or https://github.com/rangle/angular-ssr - any Angular SSR project

Do those have the same issues?

They would probably, there is a problem that I am getting, if I go http://localhost:4200 and then in the console window, I write

window.__coverage__

, i'd see the coverage data

Oh ok. So you have it on the window

Yes

Heh. OK.

Can we pair?

But

https://localhost:4200/__coverage__

is

{ coverage: null }

OH

oh

Sure, we can pair

Yeah this is interesting for me because I haven't worked in that plugin a lot and it's something i'm going to have to get used to 🙂