Sprint Blog 2 (Dec 14-Dec 15) from“Pulse news stream”

目录

I. Overview of the second Day of Sprint Progress

1. Sprint Phase Background

2. Task Completion Status in Two Days

3. Unfinished Tasks and Reasons (To Be Prioritized Next Sprint)

II. Core Deliverables

III.Problems Encountered and Solutions

Code Conflict Issue

IV.Task Plan for the Next Day

I. Overview of the second Day of Sprint Progress

1. Sprint Phase Background

Building on Day 1’s progress (front-end/back-end basic communication, homepage news list docking, initial FZU Column connection), this two-day sprint focused onclosing Day 1’s core pending tasks, repairing known bugs, and optimizing the stability of existing functions—ensuring basic modules operate smoothly to prepare for the news bookmarking function (the key task of the next phase).

2. Task Completion Status in Two Days

• Login Module Full-Process Integration (Pending from Day 1)The front-end and back-end teams unified the password encryption algorithm, fixed the back-end token generation vulnerability, and completed end-to-end debugging of the login function. Users can now seamlessly complete the full workflow (enter credentials → back-end verification → token storage → page redirection); auxiliary features like "remember password" and "incorrect password prompts" passed all test cases, and login status remains stable after page refreshes.
• Closed-Loop Repair of Day 1’s Bugs
  • The front-end team optimized the anti-shake logic for the homepage news list’s pull-to-refresh function (setting a 500ms request interval threshold), completely eliminating occasional duplicate data loading.
  • The back-end team corrected the route configuration of the FZU Column detail page and adjusted front-end/back-end parameter transfer rules, fully resolving the 404 error.All fixed bugs were verified by the testing team and marked "Closed" in the bug management tool.
• Basic Optimization of Existing FunctionsThe team optimized the response speed of the homepage news list interface: by compressing the returned data format, the average loading time was reduced from 1.1 seconds to 0.7 seconds, improving the page opening experience.

3. Unfinished Tasks and Reasons (To Be Prioritized Next Sprint)

• Unfinished Task: News bookmarking function development (users cannot save favorite news to the personal center yet).
  • Reason Analysis: Extra time spent on debugging the login module’s token stability delayed the start of this task (the function requires a new database table and front-end interactive components).
  • Compensation Plan: The back-end will design the news-bookmark relationship table on the first morning of the next sprint; the front-end and back-end will complete parallel development and joint debugging in the afternoon, ensuring the function is launched before the third sprint blog is published.

II. Core Deliverables

Code debugging and modification：

Linking and Information Entry for Fuzhou University Column：

III.Problems Encountered and Solutions

Code Conflict Issue

• Problem Description: When synchronizing the login module’s optimized code to the team repository, a conflict occurred (two members edited the same authentication logic file), causing partial code loss.
• Solution: Rolled back to the latest stable version, merged the modified content manually, and established code submission rules: (1) Pull the latest repository code before editing; (2) Notify the team when modifying core function files.
• Follow-up: A 10-minute team sync will be held at the start of the next sprint to review these rules.

IV.Task Plan for the Next Day

1. Prioritize Pending Task: Complete the news bookmarking function
   • Back-end: Design and create the news-bookmark relationship table; develop "add bookmark" and "query bookmark list" interfaces.
   • Front-end: Add a bookmark button to news cards; develop the bookmark list page in the personal center.
2. Stabilize Existing Functions: Conduct regression testing on the login module and FZU Column pages to ensure no new bugs are introduced.
3. Small Optimization: Adjust the FZU Column’s text line spacing (based on user experience feedback) to improve readability.