Unit tests raise errors with exit code 3221225725 on Windows

[ryo-utsunomiya]

Versions

• vee-validate: 2.1.5
• vue: 2.5.21
• Node: 10.14.1

Describe the bug

On Windows, a Vue component test using VeeValidate raise errors with exit code 3221225725. I'm wondering if this is misuse of vee-validate in unit test or vee-valdiate issue.

My test code is:

import VeeValidate from 'vee-validate';
import { expect } from 'chai'
import { shallowMount, createLocalVue } from '@vue/test-utils'
import HelloWorld from '@/components/HelloWorld.vue'

const localVue = createLocalVue();
localVue.use(VeeValidate);

describe('HelloWorld.vue', () => {
  it('renders props.msg when passed', () => {
    const msg = 'new message'
    const wrapper = shallowMount(HelloWorld, {
      propsData: { msg },
      localVue,
    })
    expect(wrapper.text()).to.include(msg)
  })
})

To reproduce

https://github.com/ryo-utsunomiya/poc-vee-validate-stack-overflow
This repository contains a sample Vue application with vee-validate, mocha and vue-test-utils.

You can reproduce the problem with following commands:

1. git clone https://github.com/ryo-utsunomiya/poc-vee-validate-stack-overflow
2. cd poc-vee-validate-stack-overflow
3. yarn install
4. yarn test:unit

When I run yarn test:unit on my Windows PowerShell, console output looks like this:

Expected behavior
The test passes without warnings/errors.

[logaretm]

Make sure to use sync: false in mounting/shallowMounting options when testing with vee-validate, vee-validate relies heavily on asynchronous rendering, so it wouldn't play nice with vue-test-utils synchronous behavior until vuejs/vue-test-utils#1062 is merged.

const wrapper = shallowMount(HelloWorld, {
  propsData: { msg },
  localVue,
  sync: false
});

Bonus tip: use flush-promises after triggering validation (via model change or event dispatch or test-utils trigger helper), since validation happens asynchronously.

[ryo-utsunomiya]

Setting sync: false perfectly worked. Thanks, you saved my day!