To do before release

[eddyerburgh]

Hi guys, vue-test-utils has been in beta for a couple months now, and the feedback we've got has been really helpful.

There are a few things left to do before we release 1.0.0:

• Add deprecation notice to hasClass, hasAttribute, and hasProp, in favor of classes, attributes, and props
• Add support for async components via Code Splitting Code splitting support #61
• Fix bug with keyed transitions Vue.nextTick() required with transitions. #52
• Add docs for testing components that have asynchronous calls add section to docs on testing components that include promises #151
• Add support for inheritAttrs Attr inheritance and InheritAttrs/InheritListeners #146
• Add support for testing scoped slots Test slot scope #156
• Improve support for vue.extends findAll with Vue extended component causing errors #248
• Improve find to find Vue components without names
• Handle functional components in find Can't find functional component #296
• Add setChecked, setValue, and setSelected methods Add setChecked and setValue methods #530
• Improve support for extended components
• Improve scopedSlots option. Issue Method to test scoped slots API #809
• Fix synchronous bugs

If anyone has any additional items they think should be added to the list, leave a comment 🙂

[lmiller1990]

I think you have the wrong issue reference for Add docs for testing components that have asynchronous calls ?

I am interested in writing docs for this! This basically refers to anything using async or a Promise, right?

Maybe we can put it under the guides section.

[eddyerburgh]

Yes, I think we should add it to the guides section. That would be great if you could write it 🙂

[lmiller1990]

I would like to do this, I will have time after the 19th.

Edit: started here https://github.com/lmiller1990/vue-test-utils/blob/add-async-guide/docs/en/guides/testing-async-components.md

Also, I think we should add something about what to test. A lot of people have problems, when they are testing things using vue test utils that it shouldn't be used for (like testing other people's components).

Not directly related to this library, but I think providing an official library that will become a big part of the ecosystem, some solid guides on how to use it, and not just what it does but what it does not/should not do would be valuable.

I gave a presentation last night about vue-test-utils at v-meetup in Tokyo, and talked to a bunch of people, and one of the main feedback points was "better ways to select things, like calendar inputs".

I think what people are doing is unit testing components that have child components which wrap and , which I don't think should be the job of vue-test-utils (unless of course you are authoring a input wrapper component). The line between unit tests and integration tests is pretty blurred for a lot of people.

[eddyerburgh]

Yeah I agree, I'll add it to the list

[38elements]

IMHO,
I think it is better that Add docs on what/ how to test is in cookbook.

[lmiller1990]

@38elements I can see your line of thinking. I feel like some test specific guides, with lots of details, would be great to include with vue-test-utils docs, and some more general ones referring to vue-test-utils in the cookbook.

I made PR #282 with a detailed guide about async components, but something more general I think would be great. I'll post in the cookbook repo. Thanks for your input!

[robcresswell]

Is it possible to get beta.9 released in the meantime? Having .attributes() broken is a bit of pain 😄

[eddyerburgh]

@robcresswell just released

[38elements]

Would you please update document page?

[robcresswell]

Great work @eddyerburgh !

Is there a bug on functional components or I'm missing something?

<template functional> or <script>export default { functional: true }</script> doesn't work.

mount.context can only be used when mounting a functional component

[eddyerburgh]

Hi lago, please create a separate issue of this with a minimal reproduction

…

On 18 Jan 2018 07:41, "Iago ♨️" ***@***.***> wrote: Is there a bug on functional components or I'm missing something? <template functional> or <script>export default { functional: true }</script> doesn't work. mount.context can only be used when mounting a functional component — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#246 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AMlbW2bGBJ5fnZzmpgTmcF6PUnzLJvAGks5tLvWjgaJpZM4Q8Khu> .