Feature: setSelected() with value or setValue() on select

[VictorCazanave]

What problem does this feature solve?

In my tests I often use the same value (stored in a variable) to select an option and check the assertion.

Then the current setSelect() is not very convenient :

const values = ['value0', 'value1']
const options = wrapper.find('select').findAll('option')
const index = 1
options.at(index).setSelected()
expect(/* something */).toEqual(values[index])

Same when selecting an option by value :

const newValue = 'value1'
const option = wrapper.find('select').find(`option[value="${newValue}"]`)
option.setSelected()
expect(/* something */).toEqual(newValue)

So I prefer to use :

const select = wrapper.find('select')
const newValue = 'value1'
select.element.value = newValue
select.trigger('change')
expect(/* something */).toEqual(newValue)

What does the proposed API look like?

const select = wrapper.find('select')
select.setSelected('value')
// or
select.setValue('value') // Trigger 'change' event instead of 'input'
// or a new method
select.setSelectedValue('value')

[VictorCazanave]

@eddyerburgh if you agree with this feature, I may have time to (try to) make a PR this week 😏

[eddyerburgh]

I like the idea, but not sure how it would work when you have multiple options with the same value?

[VictorCazanave]

I always use options with unique values.
For what kind of use case do you need options with the same value?

Maybe this feature should also accept an Array as parameter to handle multiple select:

select.setSelected(['value0', 'value1']);

[eddyerburgh]

Ok, how about updating setValue to set the value of a selected element. Then there's no need to handle multiple options with the same value

[VictorCazanave]

It sounds good to me

[VictorCazanave]

May I create a PR or does this feature need more discussion/approval?

[eddyerburgh]

Yes you can create a PR :)