🧪 Testing Guidelines¶
Testing is a critical part of our development process to ensure stability and quality of our products.
Manual Testing¶
-
Always perform manual testing locally before pushing any code.
Verify that your changes work as expected across supported browsers and devices. -
Test user flows, edge cases, and error handling to catch issues early.
Automated Testing¶
-
Write unit tests for all new features and bug fixes wherever possible.
This helps catch regressions and improves code reliability. -
Use existing test frameworks and follow the current test conventions in the repo.
-
Ensure tests cover both expected and unexpected input scenarios.
CI Testing¶
- Our CI pipeline runs all automated tests on every PR.
- Do not merge code unless all tests pass successfully.
Summary¶
| Step | Description |
|---|---|
| Manual Testing | Test your changes locally |
| Write Unit Tests | Add automated tests if possible |
| Verify CI Passes | Ensure all tests pass before merge |
Need Help?¶
Ask in #product-core
Testing well helps us deliver robust and reliable software our users can trust. ✅