List view
- Overdue by 2 month(s)•Due by December 5, 2025•2/2 issues closed
Backend Implementation All core backend features must be implemented RESTful API endpoints should be developed for main entities. API documentation should be available and accessible through FastAPI Testing & Quality Assurance Each pull request should have an associated test that successfully passes before the code is merged. At a minimum, the testing should include both unit tests and integration tests. The API endpoints should be thoroughly tested. A working Continuous Integration (CI) pipeline set up using GitHub Actions. Evidence of test execution (test reports, screenshots, or coverage reports) Folder in GitHub containing screenshots and coverage reports Demonstrate the use of multiple testing methodologies, such as mocking, equivalence partitioning, fault injection, and exception handling Identify and document pull requests (PRs) that demonstrate the use of these different testing approaches applied to the submitted code. Each student must have at least 10 pull requests showcasing this variety of testing methods. Code Quality & Best Practices Code structured and modular, following chosen architecture (from Milestone 2) Identify the classes implementing the design patterns from M2. Use of consistent naming conventions and documentation/comments. Following SE best practices: Frequent and meaningful commits. Proper branching strategy Well-documented pull requests Code reviews with comments Issue tracking and management. Remember, each student should work on 2-4 issues each week Comments shouldn't explain the implementation of the code. Only meaningful comments. Refactoring of code Identify and document the pull requests (PRs) that demonstrate proper refactoring activities. Each student must have at least five pull requests showcasing a refactoring. Deployment (Basic) Backend runs in a deployable environment (containerized). Demonstrate the running backend during the milestone session Traceability The GitHub backlog must be updated to reflect both completed and pending user stories. Using the traceability matrix from Milestone 1, verify which user stories and requirements have been implemented.
Overdue by 3 month(s)•Due by November 21, 2025•53/53 issues closed