Trigger 'input' for few input fields

[sheb-gregor]

I tried to test the correct bindings of the v-model and encountered the following problem: changing the values of the 'input' elements and calling the .trigger('input') method always only triggers the first one.
So first assert pass, seconds fails.

 it('should render correct contents', () => {
    const wrapper = mount(Login, { store })
    expect(wrapper.find('h1')[0].text()).to.equal('Login')

    const username = wrapper.find('input')[0]
    const password = wrapper.find('input')[1]
    username.element.value = 'test@mail.com'
    password.element.value = 'test password'

    username.trigger('input')
    expect(wrapper.vm.credentials.username).to.equal('test@mail.com')
    password.trigger('input')
    expect(wrapper.vm.credentials.password).to.equal('test password')
  })

Problem was solved by reorganizing of variables declarations.
In the code below all assertions pass.

  it('should render correct contents', () => {
    const wrapper = mount(Login, { store })
    expect(wrapper.find('h1')[0].text()).to.equal('Login')

    const username = wrapper.find('input')[0]
    username.element.value = 'test@mail.com'
    username.trigger('input')

    const password = wrapper.find('input')[1]
    password.element.value = 'test password'
    password.trigger('input')

    expect(wrapper.vm.credentials.username).to.equal('test@mail.com')
    expect(wrapper.vm.credentials.password).to.equal('test password')
  })

[eddyerburgh]

I don't think there's an easy solution to this, apart from restructuring the test. Like you did. I'll leave this issue open and I can look into it in the future, but for the moment your rewrite is the best solution.