Sports APP function test

·content

1. Plan description
- 1. Test product
- 2. Test schedule
2. Description of requirements
3. Test description
Fourth, the conclusion statement
5. Job description
6. References

1. Description of the plan:

1. Test the product

We chose the sports APP for comparison test, A product: keep , B product: Joy Running Circle

2. Test schedule

project	Content description	Estimated time (minutes)	Actual time (minutes)
Planning	1. Plan	10	10
· Estimate	· Estimate how much time the task will take	10	10
Testing Design	2. Test Design	120	150
· Analysis	· Requirements and test requirements analysis	40	30
· Design Test Cases	· Design test cases	80	120
Testing Environment	3. Build a test environment (install test tools, management tools and other related operation and support software)	30	50
Testing Implementation	4. Test Implementation	60	90
· Test	· Execute tests	60	90
Reporting	5. Report	60	130
· Test Report	· testing report	50	110
· Postmortem & Process Improvement Plan	· Review after the fact and propose a process improvement plan	10	20
	total	280	430

2. Description of requirements

1. Overall functional module division diagram

2. Detailed functional module division diagram

Note: The red font in the figure represents the function module
keep

running circle with high frequency

Comparing the above two pictures, I have selected several functional modules that are frequently used and have commonalities for further division. The results are as follows:
Account management and binding

of keep account management and binding

Joy running circle account binding

Personal data management

keep personal data

Joy running circle personal data

3. Test description

1. Design ideas

According to the previous division of functional modules, I have selected several functions that are frequently used by users for functional testing.
The test cases of this functional test are mainly tested by the scenario method in black box testing. Using this method, the internal logic of the program can be tested against the requirements.
Considering that the number of event streams of each function is small and the logic is simple, the scene construction method based on independent paths is used, and the infeasible paths that may be included in the middle are eliminated after the construction is completed.
The specific design and event flow diagram are as follows:
Note: Red is the basic event flow, and black is the alternative event flow.

1.1 Modify personal data (including avatar)

keep

Scenario 1: Elementary Stream
Scenario 2: Elementary Stream + Alternative Stream 1
Scenario 3: Elementary Stream + Alternative Stream 2 + Alternative Stream 4
Scenario 4: Elementary Stream + Alternative Stream 2 + Alternative Stream 5
Scenario 5: Basic Stream + Alternative Stream 2 + Alternative Stream 3
Scenario

1: Basic Stream
Scenario 2: Basic Stream + Alternative Stream 1
Scenario 3: Basic Stream + Alternative Stream 1 + Alternative Stream 2
Scenario 4: Basic Stream + Alternative Stream 1 + Alternative Stream 3

1.2 Change password

keep

scenario 1: elementary stream
scenario 2: elementary stream + alternative stream 1
scenario 3: elementary stream + alternative stream 2
scenario 4: elementary stream + alternative stream 3
scenario 5: elementary stream + alternative stream 4
scenario 6: basic Flow + Alternative Flow 5
Joy Run
The event flow diagram is basically the same as keep , except that it lacks the detection of whether the new password is the same as the original password, so I will not go into details
. : Elementary Stream
Scenario 2: Elementary Stream + Alternative Stream 1
Scenario 3: Elementary Stream + Alternative Stream 2
Scenario 4: Elementary Stream + Alternative Stream 3
Scenario 5: Elementary Stream + Alternative Stream 4
Scenario 6: Elementary Stream + Alternative Stream 4 stream 5

1.3 Connecting devices and applications

keep

Scenario 1: Elementary Stream
Scenario 2: Elementary Stream + Alternative Stream 1
Scenario 3: Elementary Stream + Alternative Stream 2
Scenario 4: Elementary Stream + Alternative Stream 2 + Alternative Stream 3
Scenario 5: Elementary Stream + Alternative Stream 4
Scenario 6: Basic Stream + Alternative Stream 4 + Alternative Stream 5

1.4 Binding a third-party account

keep

Scenario 1: Elementary Stream
Scenario 2: Elementary Stream + Alternative Stream 1
Scenario 3: Elementary Stream + Alternative Stream 2
Scenario 4: Elementary Stream + Alternative Stream 2 + Alternative Stream 4
Scenario 5: Elementary Stream + Alternative Stream 2 + Alternative Stream 4 + Alternative Stream 5
Scenario 6: Basic Stream + Alternative Stream 3

Happy Running Circle

Scenario 1: Basic Stream
Scenario 2: Basic Stream + Alternative Stream 1
Scenario 3: Basic Stream + Alternative Stream 2
Scenario 4: Basic Stream + Alternative Stream 2 + Alternative Stream 3
Scenario 5: Basic Stream + Alternative Stream Alternative Stream 2 + Alternative Stream 3 + Alternative Stream 4
Scenario 6: Basic Stream + Alternative Stream 5

2. Test process

The following is a brief description of the test cases for each scenario, with key test screenshots, or screenshots of the results.

2.1 Modify personal data (including avatar)

Test for keep

Scenario 1: Simply enter the data modification page from the avatar bar to modify the text information

Scenario 2: Simply enter the data modification page from the settings to modify the text information

Scenario 3: Choose to take a photo as the avatar when changing the avatar, but lack the permission to use the camera

Scenario 4: When changing the avatar, choose to take a photo as the avatar, and you have permission to use the camera

Scenario 5: Select from album when changing avatar

The test of the jogging lap

Scenario 1: Simply enter the edit profile interface and modify basic information

Scenario 2: Use a local photo to replace the avatar

Editing photos

Scenario 3: When modifying the avatar, there is no memory read permission

Scenario 4: Taking a photo as an avatar

2.2 Change password

Because keep and Joy Run have similar processes in this function, the test cases are the same.

Scenario 1: So the process is correct, and the password is successfully changed.
Scenario 2: The information is incomplete (submit directly without filling in) Scenario 3: The password format is incorrect, that is, the number of digits in the password is not within the required range.
Keep (for the original password ) Separate detection prompt from the new password) Scenario 4: The new password is not the same as the second confirmed password. Keep Joyful Scenario 5: The old password is incorrect . Keep Joyful Scenario 6: The new password is the same as the old password . If the modification is unsuccessful , the Yuerun circle can still be modified successfully