-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Description
Is there an existing issue for this?
- I have searched the existing issues
Summary
During a deep-dive to understand the codebase, I noticed that the backend test suite has an architecture in place but contains several empty test files for core API modules, such as test_issue.py and test_project.py. This proposal is to begin methodically adding test coverage to these modules, following the established "outside-in" testing philosophy and leveraging the existing base classes like AuthenticatedAPITest to ensure consistency.
Why should this be worked on?
Bolstering the test suite for these core features is a high-impact way to improve the project's long-term health. By starting to pay down this testing-related technical debt, we can make the entire application more stable and robust. As a contributor looking to help, I would appreciate any guidance on which API endpoints would be the most valuable to start with. I'm ready to begin with a small, focused Pull Request on a single endpoint to demonstrate the approach.