Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of Problem
Current testing docs only offer PW and NW as alternative solutions. WebdriverIO has released v8 which includes component testing and has dedicated docs how to get up and running when using Vue as framework.
Using JSDOM and JavaScript click events do not seem like a viable approach for testing component these days as they don't mimic user behavior at all. For example, clicks through
fireEvent
of@testing-library/vue
do not recognise whether another element is blocking the access to an element. I've done a whole set of experiments showing that using WebDriver which is a W3C web standard as automation protocol to mimic user behavior prevents stupid errors to pass through and also offers much more capabilities, e.g. user gestures.For pure component tests I personally would not advice to use JSDOM at all given that:
screen.debug()
to print the DOM tree providing a much better DXProposed Solution
As WebdriverIO as viable alternative.
Additional Information
n/a