FocusFlow α Sprint Blog Series - Test Essay

[FOCUS_2025_SE]

目录

• Overview
• 1. Test schedule
• 2. Login and Personal Center Module
• 2.1 Functional Testing
• 3. Tasks Creation, Deletion and Modification
• 3.1 Functional Testing
• 4. Focus Mode & Focus Time Count
• 4.1 Functional Testing
• 5. Homepage check-in & Overview
• 5.1 Functional Testing
• 6. Personal Center and Database
• 6.1 Functional Testing
• 6.2 Database Testing
• 7. Comprehensive Testing and Test Experience
• 7.1 Integration Testing
• 7.2 Compatibility and Usability Testing
• 7.3 Exception and Boundary Testing
• 7.4 Performance and Stability Testing
• 8. Testing Tools and Automation
• 8.1 Testing Tools Selection
• 8.2 Automated Testing Practice
• 9. Test Case Documentation
• 9. Test Case Documentation
• 10. Testing Summary and Comments

Overview

Course for This Assignment	2501_MU_SE_FZU
What are the requirements for this assignment	Web Testing
Team ID	FocusFlow
Objectives of This Assignment	Evaluation and evaluation of the website
Where are the requirements for this assignment	Fifth Assignment——Alpha Sprint

1. Test schedule

Number	FUNCTION	Test Time
1	Login and Personal Center Module	12.13 (1 day)
2	Tasks Creation, Deletion and Modification	12.15 (1 day)
3	Focus Mode & Focus Time Count	12.16-12.17 (2 days)
4	Homepage check-in & Overview	12.18-12.19 (2 days)
5	Personal Center and Database	12.20-12.21(2 days)
6	Final Test	12.22 (1 day)

2. Login and Personal Center Module

Test whether the user login and personal center modules function properly. This module implements an identity verification process based on mobile phone number, password, and dynamic verification code. It employs the bcrypt algorithm for password encryption and storage, and manages user session states through a session mechanism.

2.1 Functional Testing

• login interface: The login function realizes the authentication process based on cell phone number, password and dynamic authentication code. (Test Result: Normal)
• Login success/failure prompt: Test to see if the user's login result can be displayed normally, such as: login successfully, wrong captcha, wrong password, etc. (Test Result: Normal)
• Personal Center Homepage: The user page will be tested for its ability to clearly display the user's avatar (dynamically generated from initials), basic information, educational background, this month's check-in data, and the check-in calendar for the past 30 days. (Test Result: Normal)
• Modify personal information: Will test whether clicking on the “Edit” button opens a modal box that allows the user to change information such as name, phone number, e-mail, gender, birthday, school, education level and grade level. (Test Result: Normal)
• Password modification function: To test the password change function, click the “Change Password” button to open the password change panel. For security purposes, the new password must be verified against the current password and the new password must be the same as the confirmation password. (Test Result: Normal)
  file in the future.

  3. Tasks Creation, Deletion and Modification

  The core objective is to establish clear team coding standards, test the foundational functionality of the task management module, implement full lifecycle management and structured categorization of tasks, while ensuring data security and consistency within the system. This lays a solid foundation for subsequent iterations. The code strictly adheres to relevant standards including IEEE Std 830-1998 and GB/T 8567-2006.

3.1 Functional Testing

• Task Creation, Editing, and Deletion: Users can add new tasks via the “+ New Task” button, specifying a title, description, due date, and category. Tasks can be edited inline or permanently deleted after confirmation. (Test Result: Normal)
• Task Completion and Categorization: Test whether tasks can be grouped according to user-defined themes to achieve structured planning. (Test Result: Normal)

4. Focus Mode & Focus Time Count

Testing features related to Focus Mode, countdown timers, and study duration statistics. This development strictly adheres to IEEE Std 830-1998 and GB/T 8567-2006 standards. This module aims to create an immersive learning environment for users while enabling precise tracking and visual presentation of learning data.

4.1 Functional Testing

• Focus Mode: Offering a Focus Mode for users to choose from, suitable for times when concentration is needed. (Test Result: Normal)
• Countdown: For different learning tasks or personal preferences, we provide various countdown durations to choose from. (Test Result: Normal)
• Total Learning Time: In the personal feedback module, users can also view their total learning time. (Test Result: Normal)

5. Homepage check-in & Overview

This section describes the homepage check-in feature, the dashboard/overview elements presented after sign-in, and how they support user engagement and quick access to core functionality. Objectives include providing a clear daily check-in flow, immediate visibility of key metrics (streaks, today’s tasks, focus sessions), and secure, consistent synchronization with backend data stores. Development and testing were carried out in accordance with IEEE Std 830-1998 and GB/T 8567-2006.

5.1 Functional Testing

• Homepage Display and Navigation: The homepage loads correctly and presents essential information clearly. Users can navigate to main functional modules without errors. (Test Result: Normal)

• Daily Check-in: Users can complete daily check-ins, and the system records the status accurately. (Test Result: Normal)

• Overview Statistics Panel: The dashboard correctly aggregates and displays key metrics such as consecutive check-in days, total focus sessions, completed tasks, and weekly summaries. Data refreshes accurately after user actions such as check-in or task completion. (Test Result: Normal)

• Data Consistency and Refresh: After performing a check-in or completing a task, the homepage overview updates in real time without requiring a manual page refresh, ensuring consistency between frontend display and backend records. (Test Result: Normal)

6. Personal Center and Database

This section focuses on testing the interaction between the Personal Center module and the backend database, ensuring data persistence, integrity, and security. The goal is to verify that user-related data is correctly stored, retrieved, and updated across multiple sessions.

6.1 Functional Testing

• User Data Persistence: User profile information remains consistent after logout and re-login, confirming correct database storage. (Test Result: Normal)
• Check-in and Focus Data Storage: Daily check-in records and focus time statistics are accurately written to and retrieved from the database. (Test Result: Normal)
• Session Management: User sessions are maintained securely, and unauthorized access to personal data is prevented after session expiration. (Test Result: Normal)

6.2 Database Testing

• CRUD Operations: Create, Read, Update, and Delete operations on user-related tables (users, tasks, focus_records, check_in_records) function as expected. (Test Result: Normal)
• Data Integrity Constraints: Primary keys, foreign keys, and non-null constraints effectively prevent invalid or inconsistent data from being stored. (Test Result: Normal)
• Password Security: Passwords are stored using bcrypt hashing, and plaintext passwords are never persisted in the database. (Test Result: Normal)

7. Comprehensive Testing and Test Experience

This phase consolidates functional, integration, and basic non-functional testing to evaluate the overall stability and usability of the system before completion of the Alpha Sprint.

7.1 Integration Testing

• Frontend–Backend Interaction: All core modules (login, tasks, focus mode, check-in, personal center) communicate correctly with backend APIs. Request and response formats are consistent, and error handling is unified. (Test Result: Normal)
• Cross-Module Data Flow: Actions performed in one module (e.g., completing a task or focus session) are accurately reflected in related modules such as the homepage overview and personal center statistics. (Test Result: Normal)

7.2 Compatibility and Usability Testing

• Browser Compatibility: The system was tested on mainstream browsers (Chrome and Edge). Page layout, styles, and interactions remain consistent across environments. (Test Result: Normal)
• Usability Evaluation: Core user flows, including login, task creation, focus sessions, and daily check-in, are intuitive and require minimal learning cost. Navigation logic is clear and user-friendly. (Test Result: Good)

7.3 Exception and Boundary Testing

• Invalid Input Handling: The system correctly handles invalid inputs such as empty fields, incorrect formats, and duplicate submissions, providing clear error messages to users. (Test Result: Normal)
• Boundary Conditions: Tests were conducted on boundary values such as maximum task title length, long focus durations, and continuous check-ins over multiple days. The system remained stable without data loss. (Test Result: Normal)

7.4 Performance and Stability Testing

• Response Time: Under normal usage conditions, page loading and API response times meet expected performance requirements. (Test Result: Normal)
• Stability: Repeated operations such as frequent task updates and continuous focus sessions did not cause system crashes or abnormal behavior. (Test Result: Normal)

8. Testing Tools and Automation

8.1 Testing Tools Selection

• Manual Testing: Used during early sprint stages to quickly validate core logic and user flows.
• Browser Developer Tools: Applied to inspect network requests, debug frontend issues, and verify API responses.
• Unit Testing (Planned): Basic unit test cases for backend APIs are designed to be gradually introduced using frameworks such as unittest or pytest.

8.2 Automated Testing Practice

Automated testing was introduced incrementally. Simple API-level test scripts were written to verify critical endpoints such as login, task creation, and check-in. This approach reduces regression risks in later iterations and improves development efficiency.

9. Test Case Documentation

Test cases were designed based on functional requirements and typical user scenarios. Each test case includes test objectives, input conditions, execution steps, expected results, and actual results. This structured documentation helps ensure test coverage and facilitates future maintenance.

9. Test Case Documentation

Test ID	Module	Test Case Description	Test Type	Expected Result	Actual Result
1	Login Module	Login with correct phone number, password, and verification code	Functional Test	User logs in successfully and enters homepage	Pass
2	Personal Center	Modify personal information and save changes	Functional Test	Updated information is stored and displayed correctly	Pass
3	Task Management	Create a new task with title, category, and due date	Functional Test	Task is created and shown in task list	Pass
4	Focus Mode	Start a focus session with selected countdown duration	Functional Test	Countdown runs normally and focus session is recorded	Pass
5	Check-in Module	Complete daily check-in from homepage	Functional Test	Check-in status is saved and reflected in overview	Pass
6	Homepage Overview	Verify overview data after task completion or check-in	Integration Test	Statistics update correctly and remain consistent	Pass
6	Database	Verify persistence of user, task, and focus data after re-login	Database Test	Data remains intact and accurate	Pass

10. Testing Summary and Comments

Through systematic testing across multiple modules, the FocusFlow web project has demonstrated good functional completeness, data consistency, and overall stability during the Alpha Sprint. While most core features perform as expected, the testing process also revealed areas for improvement, particularly in performance optimization and automated test coverage.

Overall, the testing work provides strong support for subsequent development iterations. Future sprints will focus on expanding automated testing, improving performance under higher concurrency, and refining edge-case handling to further enhance system reliability and user experience.