Code coverage problem for <script setup>

[Xeyos88]

How is it possible that the <script setup> results as an uncovered branch?

[BIGScream]

I have the same issue with some first lines - this file was 100% covered weeks ago and has no changes since then.

I don't find any solutions for this

[BIGScream]

problem is not solved by updating vitest, @vitest/coverage-c8, @vue/test-utils, @vitejs/plugin-vue, @nuxt/test-utils-edge to latest versions. I think its a dependency from one of those...

[unherz]

I had a very similar problem with the same output and hint.
The problem in my case was that an conditional rendering was not covered.

Example:

        <span class="c-card__date" v-if="item.date">
          {{ $t('card.date') }}
          <time :datetime="item.date.toLocaleDateString('en-US')">{{ item.date.toLocaleDateString('en-US') }}</time>
        </span>

I had no test case specified for a missing date on my item.

Therefore the reporting in this case should be more interpreted as "these is something not covered in your template".
But the report itself is very bad for this case.

[bartduisters]

To add to the other comments.
@unherz is right that it should be interpreted as 'there is something not covered in the template'.

But, I'd expect the coverage tooling to just highlight the line in the template. Like this:

In my specific use case, I did not have the use case covered where show is false on the root element in the template.

I've also noticed that when adding an empty line as first line, it does not complain at all, it will claim 100% coverage.