Transition from Jest to ViteTest: Updating Testing Framework

[juliano-soares]

Is there an existing issue that is already proposing this?

• I have searched the existing issues

Is your feature request related to a problem? Please describe it

Our current testing framework (Jest) has limitations in terms of performance and compatibility with our project's build setup. This is leading to slower test execution times and potential conflicts with our build toolchain. We believe transitioning to ViteTest could address these issues and provide a more efficient and seamless testing experience.

Describe the feature you'd like

I'd like to transition our project's testing framework from Jest to ViteTest. This change aims to enhance our testing process by leveraging the performance improvements and better compatibility offered by ViteTest. While this transition may involve a learning curve for our team and require effort in migrating existing test suites, we believe it will result in more efficient and streamlined testing, ultimately benefiting our project in the long run.

Teachability, documentation, adoption, migration strategy

What is the motivation / use case for changing the behavior?

The motivation for changing the behavior and transitioning to ViteTest is that our other applications within the project ecosystem have already adopted ViteTest as their testing framework of choice. This standardization simplifies maintenance, ensures consistency across projects, and leverages the benefits provided by ViteTest. By aligning our project with this established practice, we aim to streamline development processes, facilitate knowledge sharing among team members, and maintain a consistent and efficient testing approach throughout the project.