wrapper.setSelected() triggers a change event even if the option is already selected

[vvanpo]

Version

1.0.0-beta.29

Reproduction link

https://codepen.io/vvanpo/pen/MWWroOK

Steps to reproduce

1. Mount a component with a <select> element.
2. Call setSelect() multiple times on one of the select element's options.
3. Observe the <select> element wrapper's emitted('change').length is equal to the number of times setSelect() was called.

What is expected?

A <select> element emits a change event only when the element value has actually changed.

What is actually happening?

setSelected() triggers a change event every time it is called, regardless of whether the underlying value was changed.

[vvanpo]

I hesitated to open this as a bug, as the documentation is explicit in saying that trigger('change') is called every time: https://github.com/vuejs/vue-test-utils/blob/v1.0.0-beta.29/docs/api/wrapper/setSelected.md

However, I believe setSelected() is generally used to mimic user interaction, not programmatic interaction. So it follows that setSelected() should behave in the same way as a user interacting with a <select> element's <option>s, which I believe will only ever fire a change event if the selection has been modified.

[dobromir-hristov]

You are correct, it only emits change event if select another option. It shouldnt be hard to see if an option is selected.

[codebryo]

@vvanpo as you said and the docs explicitly state it triggers the change event every time I don't think this is a bug. I don't think the test-utils should keep track of data and know if something has changed between two calls. If setSelected() gets called multiple times, it's fair that it does it job multiple times.

[dobromir-hristov]

@codebryo I am a bit split here. I agree with you on that one, yet I saw that selecting the same option does not trigger an event... Do we want to emulate a user action or explicitly do what the action states.. hmmmm @afontcu @JessicaSachs Opinions here?

[afontcu]

If I'm not mistaken, setChecked is not sending the event if the element is already checked

vue-test-utils/packages/test-utils/src/wrapper.js

Lines 356 to 357 in 950763f

	if (this.element.checked === checked) {
	return

...even though docs say the exact same thing regarding it being an alias of setting the right value and emitting the event.

I'd say all setXXXX methods to behave the exact same way. We could make them emulate the user or not, but in a consistent way. For the record, I'd like them to stay closer to the users.

[vvanpo]

@afontcu good find, it seems clear to me that emulating user actions is the most intuitive and useful behaviour, here.

Interestingly, that same is not true when calling setChecked() on an <input type="radio" />. It used to be, but was removed in ef66c26#diff-f8b21801dcf5dee76bc9f5f22e227ea8L516, which looks to me like a regression.

[vvanpo]

If there are no objections, I'll open a PR for this.

[JessicaSachs]

Yes please, @vvanpo