App Test Point Summary

App Test Point Summary

1. Functional Testing:
--write test cases according to the product requirements document.
--Software design document writing use case.
Note: Test cases are written according to the product requirements document.
2. Compatibility test:
Compatibility of--android versions
--Phone resolution compatibility
--Network compatibility: 2g\3g\4g\wifi, weak network, broken network
--app Cross-version compatibility
1. Compatibility test:
1> Phone different resolution support: client-supported resolution, etc.
2> phone different version of the support: 2.34.04.4, etc. in the test plan: you need to schedule a separate time for the compatibility testing of different Android systems, including the following version 2.0 and more than 4.0
3&gt: Different manufacturers of mobile phone manufacturer system support, different manufacturers will have different Android systems, such as: Millet,hammer on the market mainstream mobile phone support
4&gt. Phone different size support: 3.5 to 5.0 screen in UI display is different, to support maximum to minimum.
2. Install and uninstall the test:
1&gt: Build apk file can be installed and uninstalled on the real machine;
2>. Android phone-side universal installation tool. such as: Pea pod
3. Online Upgrade test:
1>. Verifying digital signatures
2&gt: Can be used normally after upgrade.
3&gt: Online cross-version upgrade.
3. Performance test:
--Stress test:
--Power Flow test:
--cup, memory consumption:
--app Boot Duration
--crash Rate
--Memory leaks
4. Network test:
1. Outside the network testing the main reality of the simulation of customer use of the network environment, the inspection of the customer single program in the actual network if the environment and the use of business operations.
2. External network testing mainly covers the WIFI\2G\3G\4G,.NET\WAP, telecommunications, mobile unicom, all possible combinations to test.
Principle:
1. As full coverage of the user's usage scenarios as possible, it is necessary to include various possibilities for different network permutations in the test case.
2. There is also a time when the analog signal is blocked. The impact of the client and so on. And to do the outsourcing scene test, in the Alpine, hilly, train and other special conditions for comprehensive testing
5. Interface Test:
--client End and service side interaction
--client Data updates and service-side data consistency
The--client-side update was broken.
The service end was hung when the--client was updated.
6. Business logic test:
1. Business logic test: The main test client business can be completed properly.
2. Function point test: The main test client function point is normal use
3. Relevance testing: The main test client and PC interaction, after the client processing, the PC side and the client data consistent
7. Anomaly Testing:
1. Interactive anomaly test: The client as a mobile phone characteristics testing, including the situation, such as incoming calls, SMS, low battery test, but also pay attention to mobile phone hardware, such as: Standby, Plug and unplug data lines, headphones and other operations will not affect the client.
2. Anomaly testing: Mainly including broken nets, power outages, server anomalies, such as the situation, the client can be normal processing, to ensure the correctness of the data.
Client Side performance test:
1. Benchmark performance test: mainly through the pressure server side interface and the client in different network environment response speed.
2. Large number of tests: mainly in a specific environment, the client can update a large number of data and the list of people, the client is able to handle the normal, divided into three kinds of situations:
--The first time a client uses it, it updates a large number of data and a list of people.
--The client updates a large amount of data during normal updates.
--After the client has downloaded a lot of data locally, it updates a large number of
If you want to get a further boost in testing, then you need to learn to use app testing tools. On the one hand, through the test tool can replace you do the tedious part of the work, you save more study time, on the other hand, these tools will provide you with a large number of game running data and logs, with this data you can more easily judge the cause of the problem occurred, The ability to interpret this data will be the most competitive in your future.

1. Security testing (permission)
1) Software permissions: including sending messages, making calls, linking networks, accessing mobile phone information, contact information, and so on.
2) data is stored, transmitted, etc. locally
3) input validation, authorization, data encryption, etc. that result from performing certain operations
4) Check based on various communication protocols or industry standards

2. Install and run the uninstall test
1) Verify that the app is properly installed and unloaded, and that the system resources are occupied before and after the operation and operation
2) installation Run uninstall tips, reports, etc.
3) Check the installation path, whether the file is reasonable, whether the components are registered correctly, etc.

3. UI Test
1) User Interface (menu, dialog box, window) layout, whether the style to meet user needs, text location, description is correct, the interface aesthetic degree, text picture combination is reasonable
2) User-friendliness, humanization, ease of operation, etc.

4. Function test
1) Review requirements, various considerations, the internal external and non-functional direct indirect function points, compare requirements, extraction test points
2) According to some common analysis methods, equivalence class boundary value judgment Table causality diagram scene method and so on, design test cases, covering the extracted function points
3) test each phase of the continuous tracking of defects, do a good job of updating the use cases and constantly changing the needs of the business or the requirements of the error

5. Performance Test
1) Limit test: Verify the responsiveness of the app at various boundary conditions
such as: low battery, storage full. Weak nets and other conditions
2) Responsiveness Testing: Verify that different operations can meet user response needs in various situations
3) Stress test: The use of this resource in the system under repeated long-term operation

6. Interrupt test (interference)
For example: Before the background run to telephone, text messages, download files, listen to music to see the film and other performance under different circumstances

7. Compatibility test
1) different network environment (WiFi, 2G, 3G, 4G, etc.)
2) compatible with various equipment brand models and system versions
Apple, Android (different brands, different Android versions), etc.

8. Regression test
Regression test after bug fix, full regression before online delivery, verification

9. Upgrade and update test
Every time the app version iteration update, with different network environment, and different update permissions (force update, do not force the update), to download, install, update, start running and other tests

10. Payment Test
1) Confirmation of payment results, database query
2) Whether the request message is encrypted
3) Payment of different scenarios
Sufficient amount, insufficient amount, repeat payment, no net payment, weak net payment, multi-platform payment with account, balance treasure credit card and many other payment methods, combination of different payment methods, correct password/error, payment limit, etc.

2.1 Safety Testing
2.1.1 Software permissions
1) risk of deduction: including sending text messages, making calls, connecting networks, etc.
2) Privacy disclosure risk: including access to mobile phone information, access to contact information, etc.
3) Check the application's input validity, authentication, authorization, sensitive data storage, data encryption, etc.
4) Restrict/allow use of mobile phone function to pick up the internet
5) Restrict/allow the use of mobile phone to send reception information function
6) Restrict/Allow application to register auto-start Application
7) Restrict or use local connections
8) Restrict/allow use of mobile phone photo or recording
9) Restrict/allow use of mobile phone to read user data
10) Restrict/allow use of mobile phone to write people user data
11) Detection of user authorization levels, data leaks, unauthorized access to the app, etc.
2.1.2 Installation and uninstallation security
1) The application should be properly installed on the device driver
2) Ability to locate the appropriate icon for the application on the installation device driver
3) whether to include digital signature information
4) all managed properties and their values contained in JAD files and jar packages must be correct
5) The data content displayed by the Jad file should be consistent with the content displayed by the application
6) The installation path should be able to specify
7) without the user's permission, the application cannot be pre-programmed to start automatically
8) Whether the uninstall is safe, and whether the files installed in it are all uninstalled
9) Whether the files generated during user use are prompted
10) Whether the modified configuration information is restored
11) Whether the uninstall affects the functionality of other software
12) Uninstall should remove all files
2.1.3 Data Security
1) When the password or other sensitive data is lost to the application, it will not be stored in the device, and the password will not
Be decoded
2) The password of the sender will not be displayed in clear text form
3) Passwords, credit card details, or other sensitive data will not be stored in the location of their pre-loss.
4) The individual ID or password length of the different application must be at least between 418 digit lengths
5) When the application processes credit card details, or other sensitive data, the data is not written in clear text to a separate
files, or temporary files. With 6) to prevent the application from terminating abnormally and without its temporary files, the file may
Attacked by human invaders, and then read this data information.
7) When sensitive data is lost to the application, it is not stored in the device.
8) The backup should be encrypted, the recovery data should be considered the exception of the recovery process? Communication interruption, data recovery before use should be
After verification
9) The application should consider the user's prompt information or security report generated by the system or virtual machine
10) The application can not ignore the user information or security warning generated by the system or the virtual machine, or the security police
The application should not impersonate a security warning to mislead the user by displaying misleading information before
11) Before the data is deleted, the application should notify the user or the application to provide a "Cancel" command operation
12) "Cancel" command operation can be implemented according to the design requirements of its function
13) Applications should be able to handle situations where application software is not allowed to connect to personal information management
14) When you perform a read or write user information operation, the application will send the user an action error message
15) Do not damage the side except the personal information management application without the user's explicit permission μ
16) The application reads and writes the data correctly.
17) Applications should have exception protection.
18) If important data in the database is being rewritten, the user should be notified in time
19) be able to handle the errors that occur properly
20) Unexpected circumstances should prompt the user
2.1.4 Communication Security
1) in the process of running its software, if there is a call, SMS, EMS, MMS, Bluetooth, infrared and other communications or charging, is
Can suspend the program, prioritize communication, and resume the software after processing, continue its original function
2) When the connection is established, the application can handle the interruption of the connection due to the interruption of the network connection.
3) should be able to handle communication delay or interruption
4) The application will remain working until the communication time-out, which in turn sends the user an error message indicating a connection error
5) should be able to handle network anomalies and timely notify users of anomalies
6) Disconnect when the application shuts down or the network connection is no longer in use
7) HTTP, HTTPS overlay test
--app and background services are generally interactive through HTTP, verifying that the HTTP environment is normal;
--The Public free network environment (such as McDonald's, Starbucks, etc.) to enter the user name and password, SSL authentication
To access the network, the library exception that uses the HTTP client needs to be captured.
2.1.5 Man-Machine interface security
1) Return menu always remains available
2) command has priority order
3) Sound settings do not affect the functionality of the application
4) The application must use the full-screen size applicable to the target device to display the above content
5) The application must be able to handle unpredictable user actions, such as wrong actions and pressing multiple keys at the same time
2.2 Installing and uninstalling tests
Verify that the app is properly installed, running, and uninstalled
2.2.1 Installation
1) software in different operating systems (Palm OS, Symbian, Linux, Android, IOS, Black Berry OS 6.0,
Windows Phone 7) is installed properly.
2) After the installation of the software can be normal operation, the installation of the folder and files are written to the specified directory.
3) The combination of the various options for the software installation conforms to the summary design instructions
4)) UI test of the Software Installation Wizard
5) Whether the software installation process can be canceled, after clicking Cancel, the written file is treated as a summary design note
6) Whether the process of accidental handling during software installation meets the requirements (e.g., crash, restart, power loss)
7) If the installation space is insufficient when the appropriate prompt
8) No redundant directory structures and files are generated after installation
9) for installation that requires network authentication, try it out in the case of off-screen
10) also need to test the installation manual, according to the installation manual can be installed smoothly
2.2.2 Uninstall
1) Delete the installation folder directly uninstall whether there is a prompt message.
2) test the system directly uninstall the program if there is a prompt message.
3) After testing the uninstall file, delete all the installation folders.
4) Testing of unexpected conditions during uninstallation (e.g., freezing, power-down, restart).
5) Uninstall whether to support the cancellation feature, click Cancel after the software uninstall situation.
6) The system directly uninstall the UI test, whether there is an uninstall status progress bar hint.
2.3 UI Test
Test the layout of the user interface (such as menus, dialogs, windows, and other customizable controls), whether the style meets customer requirements, text
Whether it is correct, whether the page is beautiful, text, picture combination is perfect, the operation is friendly and so on.
The goal of the UI test is to ensure that the user interface will provide the user with the appropriate access or functionality by testing the functionality of the object.
Ensure that the user interface complies with company or industry standards. Including user-friendly, humanized, easy to operate test.
2.3.1 Navigation test
1) Buttons, dialog boxes, lists and windows, etc., or navigating between different connection pages
2) is easy to navigate, navigation is intuitive
3) Whether a search engine is required
4) navigation help is accurate and intuitive
5) The style of navigation and page structure, menu, Connection page is consistent
2.3.2 Graphics Test
1) Horizontal comparison. All controls operate in a uniform manner
2) Adaptive interface design, the content according to the window size adaptive
3) page label style is unified
4) Whether the page is beautiful
5) The picture of the page should have its actual meaning and require the overall orderly appearance
6) Picture quality is high and the picture size should be as small as possible when the design meets the requirements
7) The overall use of the interface color should not be too much
2.3.3 Content Testing
1) Input box description text content and system function is consistent
2) Whether the length of the text is limited
3) Whether the text content is unclear
4) Whether there is a typo
5) Whether the information is displayed in Chinese
6) Whether there are sensitive words, keywords
7) Whether there are sensitive images, such as: copyright, patents, privacy and other pictures
2.4 Functional Testing
According to the software description or user requirements to verify the implementation of the various functions of the app, using the following methods to achieve and evaluate the functional test
Ride:
1) Use of time, place, object, behavior and background five elements or business analysis methods to analyze and refine the app user
scenarios, compare descriptions or requirements, organize the requirements that are directly related to internal, external, and non-functional, build test points, and identify
Testing standards, if there is no clear criteria for user requirements to follow, you need to refer to industry or relevant international standards or guidelines.
2) According to the characteristics of the measured function points bowl out the corresponding type of test cases to cover them, such as, the place involved in the input needs
The test types such as equivalence, boundary, negative, exception or illegal, scene rollback, association test, and so on are considered to be overwritten.
3) Track test implementation and requirement input coverage at all stages of the test implementation, timely fix business or demand understanding errors
Miss.
2.4.1 Run
1) After the app installs the test run, can open the software normally.
2) app open test, whether there is a progress prompt to load status.
3) App open speed test, whether the speed is considerable.
4) Whether the switch between the app pages is smooth and the logic is correct
5) Registration
--Same Form editing page
--User name password length
--Post-Registration Tips page
--The Front desk registration page and the Background Management page data is consistent
--after registration, in the Background management page prompt
6) Login
--Use a legitimate user login system.
--whether the system allows multiple illegal landings, and whether there are times limit.
-Use the logged-in account to log on to the system for proper handling.
--Use the Disabled account login system is correct processing.
--whether the user name, password (password) error or missing fill in the login.
-Deleted or modified users, the original user login.
--Do not enter the user password and user, repeat point (OK or Cancel button) is allowed to login.
-After landing, the landing information on the page.
--There is a logout button on the page.
--Processing of login timeouts.
7) Logout
--Write off the original module, the new module system can be handled correctly.
--Terminate the logout can return the original module, the original user.
--Write off the original user, the new user system can be handled correctly.
--Log off with an incorrect account number, password, and a disabled account with no permissions
Front and rear switch for 2.4.2 applications
1) The app switches to the background and back to the app, checking to see if it stays on the last user interface.
2) The app switches to the background, then back to the app, check the function and application status is normal, IOS4 and IOS5 version of the place
The rationale for the mechanism is different.
3) The app switch to the background, and then back to the foreground, notice whether the program crashes, function status is normal, especially for from
Background switch back to the foreground when the data is automatically updated.
4) Mobile phone lock screen unlocking after entering the app note whether it will crash, functional status is normal, especially for switching from the background
Back to the foreground when the data is automatically updated.
5) When the app is in use, when the phone comes in and then switches to the app, is the function status normal?
6) When the app process is killed, the App,app can start normally.
7) After the prompt box must be processed, switch to the background, then switch back, check whether the prompt box still exists, sometimes
The bug that the app automatically skips the Cue box appears.
8) for the data exchange of the page, each page must be the front and rear switch, lock screen test, this page most
Prone to crashes.
2.4.3 Free Login
Many apps offer a login-free feature that automatically uses the app as soon as the app is turned on with the user's identity.
1) When the app has a login-free feature, you need to consider the iOS version differences.
2) Consider the ability to enter the non-logon state normally without network conditions.
3) After switching user login, to verify the user login information and data content is updated to ensure that the original user exit.
4) According to the existing rules of Mtop, an account is allowed to log on only one machine. So, you need to check for an account login multiple
The situation of the mobile phone. The user in the original phone needs to be kicked out and given a friendly hint.
5) The app switches to the background, then back to the front of the check
6) switch to the background and switch back to the foreground test
7) After the password change, check if there is a valid identity verification of the data exchange
8) An application that supports automatic login checks if the system can be successfully logged on and the data operation is not
Miss.
9) Check that the user is actively logged out, the next time you start the app, you should stay in the login screen
2.4.4 Data Update
According to the application business rules, as well as the amount of data update, to determine the optimal data update scheme.
1) need to determine where to provide manual refresh, which need to be automatically refreshed, where manual + automatic
Refresh.
2) You need to update the data to determine where to switch back from the background to the foreground.
3) According to the reasonable allocation of business, speed and traffic, determine which content needs to be updated in real time and which needs to be updated regularly.
4) Determine the processing logic of the data Presentation section, whether it is requested from the server or cached locally, in order to have
Test accordingly.
5) Check where there is data exchange, there are corresponding exception handling.
2.4.5 Offline Browsing
Many apps support offline browsing, where local clients cache part of the data for users to view.
1) can browse local data without network condition
2) When you exit the app and then open the app, you can browse
3) switch to the background and cut back to the front desk for normal browsing
4) lock screen and then unlocking back to the application foreground can be viewed normally
5) When the data on the server is updated, the corresponding prompt will be given offline.
2.4.6 App Update
1) There is an update prompt when the client has a new version.
2) When the version is a non-mandatory upgrade version, users can cancel the update, the old version can be used normally. The next time the user launches the app
, the update prompt can still appear.
3) When the version is a forced upgrade, when the user does not make an update after the mandatory update is given, the client exits. Next launch
App, a forced upgrade prompt still appears.
4) If the client has a new version, the direct update check will update properly if the client is not deleted locally.
5) When the client has a new version, if the client is not deleted locally, check whether the updated client features are
New version.
6) When the client has a new version, if the client is not deleted locally, check whether the file with the same name can
Update to the latest version as normal. If the above cannot be updated successfully, also belong to the flaw.
2.4.7 positioning, Camera services
1) app useful to camera, location service, need to pay attention to system version difference
2) useful to location services, camera services, the need for a front and rear switch test, check whether the application is normal.
3) If the location service is not turned on, use the location service and the friendly popup will allow setting the location prompt. When determining
Allows you to automatically jump to the location setting to turn on location services when positioning is enabled.
4) Testing the positioning, camera services, you need to use the real machine for testing.
2.4.8 Time Test
The client can set the phone's time zone and timing itself, so it needs to verify the impact of the setting on the app.
--China is East 8, so when the phone is set to a time other than the East 8, see where the time needs to be displayed, whether the time
The display is correct, the application function is normal. Time typically needs to be converted to the client's time zone according to the server
Display, this kind of user experience is better. For example, the publication of a micro-blog at the server record is 10:00, at this time, Huasheng
Immediately 22:00, when the client goes to browse, if the setting is Washington time, then the display time is 22:00,
When the time is set back to the East 8 zone time, then the view is displayed as 10:00.
2.4.9 Push Test
1) Check whether the push message is sent according to the specified business rules
2) Check that the user is no longer receiving push when the push message is not accepted.
3) If the user has set a time-out period, the user cannot receive PUSH during the time-free period.
During a non-intrusive time period, the user receives the push normally.
4) When the push message is for the logged-on user, you need to check that the received push is consistent with the user's identity, and no
Mistakenly pushes other people's messages over. In general, only the last logged-on user on the phone is sent a message push.
5) test push, you need to use a real machine to test.
2.5 Performance Testing
Evaluate the time and space characteristics of your app:
1) Limit test: In the case of various boundary pressure, such as battery, storage, speed, etc., verify that the app can respond correctly.
--Install the APP when the memory is full
--Phone power off when running the app
--Disconnect the network while running the app
2) Responsiveness test: Test whether the various types of operations in the app meet user response time requirements.
--app response time for installation and uninstallation
--app the impact time of various functional operations
3) Stress test: Under the repeated/long-term operation, the system resources are not occupied abnormally.
--app load and unload repeatedly to see if the system resources are normal
--other functions repeatedly, to see if the system resources are normal
4) Performance evaluation: Evaluate the usage of system resources in typical user scenarios.
5) Benchmark Test (baseline test): Benchmarking with competitive products, product evolution comparison test, etc.
2.6 Cross-event testing
This paper presents a test method for the classification of service level and real-time characteristics of intelligent terminal applications. Cross-testing is also called an event or
A conflict test is one in which a function is executing while another event or operation interferes with the process.
Try. For example, when the app is running in front/back-end, it interacts with key applications such as incoming calls, file downloads, music listening, etc.
Try to wait. Cross-event testing is important to identify potential performance issues in many applications.
1) Whether multiple apps run at the same time affect normal function
2) Does the app run pre/background switch affect normal function
3) Call/answer phone when app is running
4) Send/Receive information when the app is running
5) Send/Receive mail when app runs
6) switch Network when app is running (2G, 3G, WiFi)
7) Browse the network while the app is running
8) Use Bluetooth to transmit/receive data while the app is running
9) When the app is running, bring your own device with your camera, calculator, etc.
2.7 Compatibility test
Main test internal and external compatibility
1) compatibility with local and mainstream apps
2) based on the different development environment and production environment, the test is under various network connections (WiFi, GSM, GPRS, EDGE, WCDMA,
Cdma1x, CDMA2000, HSPDA, etc.), the app's data and application is correct
3) compatibility with various devices, if there is cross-system support, it is necessary to check whether the various behaviors are consistent under each system.
--compatibility with different operating systems, suitability for
--compatibility of screen resolutions of different mobile phones
--compatibility of different handset brands
2.8 Regression Test
1) After a bug is fixed and a regression test is required after the new version is released.
2) The regression test after the bug is delivered, and the regression test of the full quantity use case is carried out before delivery.
2.9 Upgrade, update test
After the release of the new version, with the different network environment of the self-updating prompts and download, installation, update, start, run verification
Test.
1) test whether the function after upgrade is the same as the requirement description
2) test the function of modules related to the Upgrade module to match the requirements
3) Upgrade the installation of the test (such as the crash, power, restart)
4) UI testing of the Upgrade interface
5) upgrade Test between different operating systems
2.10 User Experience Testing
To perceive the comfort, usefulness, ease of use and friendliness of a product or service in the perspective of a subjective, ordinary consumer. Pass
Different individuals, independent spaces and non-empirical statistical multiplexing methods to evaluate the experience characteristics of products effectively
Potential customer satisfaction of the product.
1) Whether there is an empty data interface design, to guide users to perform operations.
2) Whether user guidance is abused.
3) Whether there is a non-clickable effect, such as: Your button is not available at this time, then must be gray, or take
Drop the button, or it will mislead the user
4) is the menu level too deep?
5) Are there too many branches of the interaction process
6) Whether the relevant options are far away
7) Whether to load too much data at once
8) Whether the button in the interface can be clicked in a moderate range
9) Whether the tab is not affiliated with the content, when switching the label, the content is switched
10) The operation should have primary and secondary affiliation
11) Whether to define back logic. When dealing with hardware and software interactions, the back key should be defined specifically
12) Whether there is a horizontal screen mode design, applications generally need to support the horizontal screen mode, that is, adaptive design
2.11 Hardware Environment Testing
2.11.1 gesture Operation Test
1) The effect of mobile unlock screen on running apps
2) The impact of switching networks on running apps
3) Effect of front and rear switch in running app
4) Switching of multiple running apps
5) When the app is running, shut down
6) Restart the system when the app is running
7) Charging when the app is running
8) When the app is running, kill the process and open it.
2.11.2 network Environment
The mobile phone network is mainly divided into 2G, 3G, WiFi. At present, the 2G network is relatively slow, in particular, the test should pay attention to this
Block of the test.
1) No network, the implementation needs the operation of the network, to give friendly tips to ensure that the program does not appear crash.
2) in the intranet test, you should pay attention to the selection of the external network operation when the exception processing.
3) When the network signal is not good, check the function status is normal, make sure not to submit data failure caused by crash.
4) When the network signal is not good, check whether the data will remain in the status of the submission, there is no timeout limit. If you encounter data
You should give a hint when the interchange fails.
5) When the network signal is not good, after performing the operation, when the callback is not completed, exit this page or perform other
Operation of the situation, there is no abnormal situation. This issue also often occurs with program crash.
2.11.3 server outage or test in 404, 502, etc.
Background services involve DNS, space service providers in the case will affect its stability, such as: When a domain name resolution failure occurs,
Your request to the background API is likely to have a 404 error and throw an exception. At this point, the exception needs to be properly
May cause the program to not work properly.
2.12 Interface Test
The server typically provides JSON-formatted data to the client, so we need to perform interface testing on the server to ensure
The interface provided by the server and the JSON content is converted correctly, and the corresponding return value is given for the branch and the exception stream. This block test can be
To be tested using the ITest framework. The most convenient is to use HttpClient for interface testing.
When conducting a service-side test, you need to develop an interface document.
2.13 Client Database Testing
1) General increase, delete, change, check test.
2) If the table does not exist can be automatically created, when the database table is deleted and can be self-built, the data can also automatically from
Get back and save on the server side.
3) Whether the client can save data locally when the business needs to retrieve data from the server to the client.
4) When the business needs to fetch data from the client, check whether the app data is automatically from the client when the client data exists
Data, or will it still be fetched from the server side? Check if the client data does not exist, can the app data automatically
Server-side fetch and save to client
5) If the business changes the data, after the deletion, the client and the server will have a corresponding update.

App Test Point Summary