Skip to content

Bug: setProps not behaving as expected #2675

Open
@alextana92

Description

@alextana92

Describe the bug
setProps seems to work only in isolated tests, if more tests are present it doesn't seem to be updating the component props as expected

This started failing from 2.3.1

To Reproduce
https://codesandbox.io/p/devbox/eager-waterfall-57d5kh?file=%2Fsrc%2FApp.spec.js%3A19%2C6

When running npm run test you can see that the can change prop test fails, but if you only run that test with it.only("can change prop" it passes

this was not the case before 2.3.1, wonder if this is expected behaviour or not

also worth noting that if you remove the just an extra test the suite passes.

Related information:
This happens both on vitest and jest, the Vue version doesn't seem to matter either, I've seen these errors pop up in my codebase after upgrading vue test utils from 2.3.0 to 2.4.6

behaviour seems consistent with options/composition api

Additional context

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions