App Test Point classification

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) The input validity check, authentication, authorization, sensitive data storage, data encryption and other aspects of the APP
Line detection
4) Restrict/allow access to the Internet using mobile phone function
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 phone to write user data
11) Detection of user authorization levels, data leaks, unauthorized access to the APP, etc.

Installation and uninstallation
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

Data security
1) When a password or other sensitive data is lost to the application, it is not stored in the device,
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) Different applications of the individual xxx or password length must be at least between 418 digits of length
5) do not write data in clear text when the application processes credit card details, or other sensitive data
To a separate file or to a temporary file. To prevent the application from terminating abnormally without having its side
Temporary files, files can be attacked by human invaders, and then read this data information.
6) When sensitive data is lost to the application, it is not stored in the device.
7) Backup should be encrypted, recovery data should consider the recovery process of abnormal communication interruption, etc., data recovery and then
should be verified before use
8) The application should consider the user's prompt information or security report generated by the system or virtual machine
9) The application cannot ignore user prompts or security warnings generated by the system or virtual machine, nor
Can be in the security police

Graphics testing
1) Horizontal comparison. Unified operation of the entire APP control
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

Run
After the APP installs the test run, can open the software normally.
The App opens the test and there is a progress prompt to load the status.
The APP opens the speed test to see if the speed is impressive.
Whether the switch between the APP pages is smooth and the logic is correct

Registered
Same Form Editing page
User name Password length
Post-Registration Tips page
The front registration page and background Management page data is consistent
After registering, in the Background management page prompt

Login
Log in to the system using a legitimate user.
Whether the system allows multiple illegal landings, and whether there are times limit.
Use the logged in account login system is correct processing.
Use the Disabled account login system is correct processing.
If the user name, password (password) is wrong or missing, can login.
Deleted or modified after the user, the original user login.
Do not enter user password and user, repeat point (OK or Cancel button) to allow login. --After landing,
Landing information on the page.
There is a logout button on the page.
Processing of login Timeouts

Cancellation
Unregister the original module, the new module system can be handled correctly.
Terminate logout can return the original module, the original user.
Log 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 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
3) The app switch to the background, and then back to the foreground, notice whether the program crashes, function status is normal,
This is especially true when switching back from the background to the foreground data is automatically updated.
4) Mobile phone lock screen unlocking after entering the app notice whether it will crash, functional status is normal, especially for
Switch back from the background 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 you have a prompt that must be processed, switch to the background, and then switch back to check that the prompt box is still present.
In, 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 is most likely to crash

Login Free
Many apps offer a login-free feature that automatically uses the user's identity when the app is turned on.
App.

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
The user exits.
4) If an account is allowed to log on only one machine. You need to check if an account is logged on to more than one 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 to see if the system is automatically logged in for data exchange and
The data is operating correctly.
9) Check that the user is actively logged out, the next time you start the app, you should stay in the login screen

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, and where
To manually + refresh automatically.
2) You need to update the data to determine where to switch back from the background to the foreground.
3) According to the reasonable distribution of business, speed and traffic, determine what content needs to be updated in real time, which need
Timed updates.
4) Determine the processing logic of the data Presentation section, whether it is requested from the server or cached locally,
This can be targeted to the corresponding test.
5) Check where there is data exchange, there are corresponding exception handling

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.

APP Updates
1) 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. Users in
The update prompt will still appear the next time you start the app.
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.
The next time you start the app, a mandatory upgrade prompt still appears.
4) When the client has a new version, the direct update checks if the client is not deleted locally
Normal update.
5) When the client has a new version, if the client is not deleted locally, check the updated client
Whether the feature is a new version.
6) When the client has a new version, if the client is not deleted locally, check the resources with the same name as the file
Whether the picture will be updated to the latest version as expected.
If the above cannot be updated successfully, also belong to the flaw.
7) test the app's incremental upgrade to see if the app can continue to use the upgrade after the upgrade has failed
The previous version.
8) After the release of the new version, with the different network environment of the auto-update prompt and download, install, update, start
and run validation tests.
What you need to check:
Test whether the upgraded feature is the same as the requirement description
Test whether the modules associated with the upgrade module are functionally consistent with the requirements
Upgrade a test that installs an unexpected condition (such as a crash, power outage, restart)
UI testing for the upgrade interface
Upgrade testing between different operating systems
Digital signature, upgrade overlay installation, manual overwrite installation after download, cross-version upgrade, normal after upgrade
Use. Overwrite the installation to ensure that the database has field updates, can be updated normally, otherwise it is easy to cause
App exception.

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 the front and rear switch test, check should be
Use is normal.
3) When the location service is not turned on, use the location service, will be friendly pop-up is allowed to set the location of the
Shown When you are sure to allow the positioning to be enabled, you can automatically jump to the location settings to turn on location services.
4) Testing the location, camera service, you need to use the real machine for testing

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 is displayed correctly, and whether the application function is normal. Time is usually required to convert the server time to
The client's corresponding time zone to display, so the user experience is better.
For example, the publication of a microblog on the service side of the record is 10:00, when the Washington time is 22:00, guest
When the user is browsing, if Washington time is set, the displayed time is 22:00, when
When you set the time back to East Zone 8, the view is displayed as 10:00

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 is not received during the time-free period
PUSH. 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 and user identity
Match, without mistakenly pushing 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.

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 whether the APP
can respond correctly.
Install app when memory is full--the phone loses power when running the app--disconnect the network when 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.
The APP is loaded repeatedly to see if the system resources are normal
Other functions are repeated to see if system resources are working properly
4) Performance evaluation: Evaluate the usage of system resources in typical user scenarios.
Testable aspects-Installation and startup time-CPU consumption-memory consumption-consumption of traffic-power
Consumption-backend, testing whether the various types of operations in the APP meet user response time requirements, mainly testing
Point in the speed, 2g,3g,wifi, 4g must be covered to-the backend has network concurrency

Cross-event testing
This paper presents a test method for the classification of service level and real-time characteristics of intelligent terminal applications. Cross Test
Also known as an event or conflict test, refers to a feature that is in the process of executing while another event or action
A test that interferes with the process.
such as: The APP in front/background running state with the call, file download, music listening and other key applications of the interaction
Condition testing, and so on. 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 message when app is running
5) Send/Receive mail when APP runs
6) Switch Network when APP is running (2G, 3G, 4G, 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.

Compatibility testing
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 equipment, if there is cross-system support, you need to check whether the system, the various lines
To be consistent
Compatibility with different operating systems, suitability for
Compatibility of screen resolutions for different phones
Compatibility of different phone brands

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
Degree. Effective evaluation of product experiences through different individuals, independent spaces and non-empirical statistical multiplexing methods
The 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, it must be gray
Or remove 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 there is a horizontal screen mode design, applications generally need to support the horizontal screen mode, that is, adaptive design

Hardware environment Testing
Gesture Manipulation 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.

Network environment
The mobile phone network is mainly divided into 2G, 3G, WiFi.
At present, the 2G network phase is relatively slow, especially in testing the test of this block.
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, ensure that the failure to submit data 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 the data exchange fails to give a hint.
5) When the network signal is not good, after performing the operation, when the callback is not completed, the exit of this page or
If the user performs other operations, there is no exception to the situation. This issue also often occurs with program crash.
Note: The general can choose in the subway, bus, elevator, tunnel lights representative places for testing.

Summarize

1. UI Testing
The app's main core UI is consistent with the actual design, and the interaction issues suggest that you can first
The product manager confirms that the validation has been approved before the development implementation changes or optimizations are made
2. Functional Testing
Verify the app's functions according to the software description or user requirements;
As with other tests, there is no big difference, so check out the previous test points to comb the article
3. Interrupt Testing
Test the disruption that the user is experiencing when they are actually using the app.
such as: network disconnection, switch networks, power outages, to call/SMS, listen to music, switch to other apps,
Turn on notifications for other apps, use when low power, etc.
4. Compatibility and adaptation testing
New and old versions of compatibility tests on functional, logical levels, the same app running in different system versions,
Compatibility testing between different models: the interface Compatibility test ensures that most
can be perfected;
Apps are guaranteed to run on different system versions: screen, system version, etc. (the number of system bits must be
Third-party cloud platform
Verify APP behavior in different supported languages.
5. Safety Testing
APP security testing is roughly divided into the following categories:
1) from the local storage of data to data transmission, processing and remote access, and other aspects, based on the corresponding
Safety standards/industry standards to evaluate the security features of the APP;
Learn from some of the successful experiences in WEBAPP and cybersecurity testing to cut in smart terminal APP testing
or suitable for distribution;
2) Detection of user authorization level, data leakage, unauthorized access to the APP;
3) The input validity check, authentication, authorization, sensitive data storage, data encryption and other aspects of the APP
To detect potential safety problems;
4) See if the APP meets the requirements based on a variety of communication protocols or the appropriate industry security standards.
6. On-Line testing
Online testing is the product must be completed after the launch, this part can be based on the scenario of regression testing,
Where the network environment to cover all over again

App Test Point classification