What tests are expected when submitting a pull request?

[Suhebdevtechnosys]

Select Topic Area

Question

Body

Before you send your code changes for review (a pull request), what kinds of tests should you run to make sure your changes don’t break anything?

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[iyawnnn]

Before submitting a pull request, you should run the following tests to ensure your changes don’t break anything:

1. Unit Tests: Run the unit tests for your changes to make sure the individual functions or components behave as expected.
2. Integration Tests: Verify that your changes work well with other parts of the codebase and ensure the different components integrate correctly.
3. Linting/Code Style Checks: Make sure your code adheres to the project's style guidelines (e.g., using ESLint, Prettier) to ensure consistency.
4. Build Tests: Ensure that the code compiles and that the application can be built without errors.
5. Regression Tests: Run tests to make sure that your changes haven’t unintentionally broken existing functionality.
6. Manual Testing (if applicable): For UI/UX changes or complex features, manually test the functionality in the local development environment to ensure everything behaves as expected.

Running these tests before submitting a pull request helps maintain the integrity of the codebase and speeds up the review process.