You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As the team is currently migrating the frontend to React and TypeScript, I would like to propose a discussion around incorporating unit tests as part of this migration process.
Why This is Important
Opportunity to Build a Strong Foundation: Since new pages and components will be introduced during the migration, this is an ideal time to integrate unit tests. It ensures that the new code is robust and maintainable from the start.
Improved Code Quality: Unit tests will help catch bugs early in the development cycle, reducing the risk of regressions and improving overall code quality.
Long-Term Benefits: Establishing a culture of writing unit tests now will make future development smoother and more reliable.
Proposed Approach
Use a preferred unit testing library (e.g., Jest, React Testing Library, etc.) to write tests for the new components and pages.
Discuss and finalize the testing strategy and library in a dedicated Slack channel to ensure alignment across the team.
Next Steps
Initiate a discussion in the Slack channel to gather input from the team on the preferred testing library and approach.
Align on a strategy for writing unit tests alongside the migration process.
Document the agreed-upon approach for consistency moving forward.
Let’s use this opportunity to not only modernize the frontend but also improve the overall quality and reliability of our codebase.
The text was updated successfully, but these errors were encountered:
Description
As the team is currently migrating the frontend to React and TypeScript, I would like to propose a discussion around incorporating unit tests as part of this migration process.
Why This is Important
Proposed Approach
Next Steps
Let’s use this opportunity to not only modernize the frontend but also improve the overall quality and reliability of our codebase.
The text was updated successfully, but these errors were encountered: