Bug: expose props can not access in test case.

[jason-chang]

Describe the bug
defineExpose can works fine in the browser, but does not work in the test case.
Got error like ⬇️

To Reproduce
To reproduce this problem I created a demo and put it in the CodeSandbox.

The link is here ⬇️

https://codesandbox.io/p/github/jason-chang/test-utils-bug/main

Components in src/components/Case.vue
For test cases, see src/components/tests/case.test.tsx
The browse test code is in src/App.vue

Expected behavior

You want defineExpose exported projects to be properly accessible in both browser and test case.

Related information:

Additional context

[cexbrayat]

Hi @jason-chang

Thank you for the repro.
This is interesting and probably need to be fixed. We expose everything automatically on wrapper.vm, even without defineExpose, to make tests easier. But maybe we need some special handling for the aliases

If you're interested in contributing, there are tests in expose.spec.ts. You can try to add a test with an alias if there is none. The code to fix will be in vueWrapper.ts, around

test-utils/src/vueWrapper.ts

Line 23 in ba53cfb

function createVMProxy<T extends ComponentPublicInstance>(

[erikkkwu]

I'm not sure if implementing it this way in createVMProxy is a good approach, because it depends on the unref method

[jason-chang]

@cexbrayat Thank you for your reply.
I'm not sure I have what it takes, to solve this problem 😂, so maybe let me try tomorrow.
And I'm not sure if this is a @vue/test-utils issue or a @vue/compile-sfc issue? What do you think?

[cexbrayat]

I'm pretty sure it's a test-utils problem. You can start by adding a unit test expose.spec.ts and see if it reproduces the problem. If it's too hard to fix no worries, someone from the team will take a look when we get some time 😉. Thanks!

[jason-chang]

@cexbrayat ok👌

[jason-chang]

@cexbrayat @erikkkwu Thanks your tips, I tried to create a pull request to fix & test this bug. #2125
Please review and decide whether to merge or not.