coverage report is wrong!!!

[noprogram-programmer]

counter.vue

<template>
    <div>
      <span class="count">{{ count }}</span>
      <button @click="increment">Increment</button>
    </div>
</template>
<style>
</style>
<script>
export default {
  name: "counter",
  data() {
    return {
      count: 0
    };
  },

  methods: {
    increment() {
      this.count++;
    }
  }
};
</script>

counter.test.js

import { mount } from "@vue/test-utils";
import Counter from "./counter.vue";

describe("Counter", () => {

  const wrapper = mount(Counter);

  const vm = wrapper.vm;

  it("rendenr correct to 0", () => {
    expect(wrapper.html()).toContain('<span class="count">0</span>');
  });

  it("is a button", () => {
    expect(wrapper.contains("button")).toBe(true);
  });

  it("click a button to increment count", () => {
    expect(wrapper.vm.count).toBe(0);
    const button = wrapper.find("button");
    button.trigger("click");
    expect(wrapper.vm.count).toBe(1);
  });
});

Problem

Mark the red box, i 'm not find the uncoverage line of 33,34 and branch 50% .Please resolve my doubts.

[kevinmarrec]

@eddyerburgh Any update on this ?

On my side I have :

I couldn't be able to have a proper ts-jest + vue-jest with 100% Coverage even with empty component :/

EDIT : It's working (100% coverage) if I use Vue.extend, it seems that's something goes wrong using @Component TypeScript Class Decorator.

[araujrafa]

I have the same problem, has anyone found a solution?

[kevinmarrec]

@araujrafa I got it working but I don't honestly remember how (I mean I don't remember how looked like my "not-working" configuration 😅). Can you please tell me what's your app context: is it using Nuxt or/and Vuetify ? Then I'll be able to help you 😉

[eddyerburgh]

Yes, I'm working on improving source map support. My aim is to get a beta version out within the next month. If anyone would like to help, this is the last major work to be done—#114

[eddyerburgh]

I've release 4.0.0-beta.0. Please use that version to see if it fixes the coverage issue. If not, please create a new issue with a runnable reproduction.

This issue is being tracked in #56