Shulou(Shulou.com)06/03 Report--

With the Internet, big data era continues to advance, evolution. The field of mobile development has gained popularity, and APP development has sprung up like a flood. The following are the test points for the sorted app:

First, let's familiarize ourselves with the basic process of app testing:

1.1 Test cycle

The test cycle can determine the test time according to the development cycle of the project, the general test time is two or three weeks (that is, 15 working days), and the testing time can be appropriately shortened or extended according to the situation of the project and the quality of the version. Confirm the project schedule with the supervisor before formal testing.

1.2 Test Resources

Check the test resources before the test task begins.

-- Product functional requirements document

-- Product prototype diagram

-- Product effect drawing

-- behavior Statistical Analysis definition document

-- Test equipment (ios3.1.3-ios5.0.1;Android1.6-Android4.0;Winphone7.1 and above; Symbianv3/v5/NokiaBelle, etc.)

Others.

1.3 Daily newspaper and product launch report

1) the tester needs to send a test daily to the tested project every day.

2) the contents of the test daily are:

-- grading the quality of the current test version

Give examples of more serious problems and prompt developers to modify them first.

-- evaluate the overall situation of the version.

3) before the product is launched, the tester sends the product launch report.

4) the contents of the launch report are:

-grading the quality of the current version

-attach test reports (functional test report, compatibility test report, performance test report and app available performance standard results)

-- summarize the basic situation of the online version. If there are any remaining problems, solutions must be listed and documented.

Tools / raw materials

Mobile device (Android,iOS...)

APP

Network communication equipment (routers, etc.)

Methods / steps

First, safety testing:

1. Software permissions

1) deduction risk: including SMS, phone call, network connection, etc.

2) risk of privacy disclosure: including access to mobile phone information, access to contact information, etc.

3) check the input validity check, authentication, authorization and data encryption of App.

4) restrict / allow access to the Internet using mobile phone functions

5) restrict / allow the use of mobile phones to send and receive messages

6) restrict or use local connections

7) restrict / allow the use of mobile phones to take photos or recording

8) restrict / allow the use of mobile phones to read user data

9) restrict / allow to write user data using mobile phone

10) restrict / allow applications to register automatic startup applications

two。 Install and uninstall security

1) the application should be installed correctly on the device driver

2) the corresponding icon of the application can be found on the installation device driver

3) the installation path should be able to specify

4) without the permission of the user, the application cannot be set to start automatically in advance

5) whether it is safe to uninstall and whether all the files installed are uninstalled

6) whether there is a prompt to uninstall the files generated during the use of the user

7) whether the modified configuration information is restored

8) whether the uninstall affects the functionality of other software

9) Uninstall should remove all files

3. Data security

1) when a password or other sensitive data is entered into the application, it is not stored in the device, and the password is not decoded.

2) the password entered will not be displayed in clear text.

3) passwords, credit card details or other sensitive data will not be stored in their pre-entered locations.

4) the personal × × or password length of different applications must be at least 4-8 digits long.

5) when the application processes credit card details or other sensitive data, it does not write the data in clear text to other separate or temporary files. To prevent the application from terminating abnormally without deleting its temporary files, the files may be attacked by people and then read the data information.

6) when party building sensitive data is entered into the application, it will not be stored in the device.

7) applications should consider user prompts or security warnings generated by virtual machines

8) the application should not ignore the user prompts or security warnings generated by the system or virtual machine, let alone use the display misleading information to deceive the user before the security warning is displayed, and the application should not simulate the security warning to mislead the user.

9) before the data is deleted, the application should notify the user or the application to provide a cancel command.

10) the application should be able to handle situations when the application is not allowed to connect to personal information management.

11) when reading or writing user information, the application will send an error message to the user.

12) do not damage or delete anything in the personal information management application without the express permission of the user.

13) if important data in the database is about to be rewritten, users should be informed in a timely manner.

14) be able to deal with errors reasonably.

15) the user should be prompted in case of accident.

4. Communication security

1) in the process of running the software, if there are incoming calls, SMS, Bluetooth and other communications or charging, whether the program can be suspended, priority should be given to the communication, and after processing, the software can be restored normally and its original function can be continued.

2) when a connection is created, the application can handle the broken network connection, which in turn tells the user that the connection is broken.

3) should be able to handle communication delays or interruptions.

4) the application will keep working until the communication times out, which in turn gives the user an error message indicating a link error.

5) should be able to handle network anomalies and inform users of anomalies in a timely manner.

6) when the application closes the network connection and is no longer in use, it should be closed and disconnected in time.

5. Man-machine interface safety test

1) the return menu should always be available.

2) orders have priority order.

3) the setting of sound does not affect the function of the program.

4) the setting of sound does not affect the function of the application.

5) the application must be able to handle unpredictable user actions, such as incorrect actions and pressing multiple keys at the same time.

Second, installation and uninstallation testing:

Verify that App is properly installed, run, uninstalled, and the use of system resources before and after the operation:

1. Installation

1) whether the software can run normally after installation, and whether the installed folders and files are written to the specified directory.

2) whether the combination of the options for software installation is in line with the summary design description.

3) UI test of the software installation wizard

4) No extra directory structure and files are generated after installation.

two。 Unloading

1) whether there is a prompt to test whether the system uninstalls the program directly.

2) Test whether all installation folders are deleted after uninstallation.

3) whether the uninstall supports the cancel function, and the software is uninstalled after clicking cancel.

4) whether there is an uninstall status progress bar when the system uninstalls the UI test directly.

3. UI test:

1) Test whether the layout and style of the user interface (such as menus, dialogs, windows and other controls) meet the requirements, whether the text is correct, whether the page is beautiful, whether the combination of text and pictures is perfect, whether the operation is friendly, etc.

2) the goal of UI testing is to ensure that the user interface provides users with corresponding access or browsing functions by testing the functions of the objects. Ensure that the user interface meets company or industry standards. It includes user-friendly, humanized and easy-to-operate testing.

1. Navigation test

1) buttons, dialogs, lists, windows, etc., or navigation between different connected pages.

2) whether it is easy to navigate and whether the navigation is intuitive.

3) whether a search engine is needed.

4) whether the navigation help is accurate and intuitive.

5) whether the navigation is consistent with the page structure, menu, and the style of connecting pages.

two。 Graphic test

1) horizontal comparison, the operation mode of each control is unified.

2) Adaptive interface design, the content is adaptive according to the size of the window.

3) whether the style of the page tag is uniform.

4) whether the page is beautiful or not.

5) the picture of the page should have its practical meaning and require the overall order and beauty.

3. Content testing

1) the input box indicates whether the content of the text is consistent with the function of the system.

2) whether the length of the text is limited.

3) whether the meaning of the text is unclear.

4) whether there are any wrong words.

5) whether the information is displayed in Chinese.

Fourth, functional testing:

Verify each functional implementation of App according to the software description or user requirements, and use the following methods to implement and evaluate the functional testing process:

1) analyze and refine the user usage scenarios of App by using the five elements of time, place, object, behavior and background or business analysis, compare the instructions or requirements, sort out the internal, external and non-functional requirements, build the test points, and define the test standards.

2) according to the characteristics of the tested function point, list the corresponding types of test cases to cover it, for example: where the design input needs to consider equivalence, boundary, negative, exception, illegal, scene rollback, association testing and other test types to cover it.

3) track the coverage of test implementation and requirement input in all stages of test implementation, and correct business or requirement understanding errors in time.

1. Running

1) after the App installation is completed, the software can be opened normally.

2) App opens the test to see if there is a progress prompt for the loading status.

3) whether the switching between App pages is smooth and whether the logic is correct.

4) Registration

Edit the page with the form

Username password length

Tips page after registration

Whether the data of the registration page of the foreground and the management page of the background are consistent.

After registration, the page prompts in the background management

5) Log in

Use a legitimate user to log in to the system

Whether the system allows multiple illegal logins, and is there a limit on the number of times?

Whether to log in to the system using the already logged-in account is handled correctly.

Can I log in if the user name and password (password) are wrong or omitted?

Delete or modify the user, log in with the original user name

Login is allowed without entering the user password and repeating the OK / cancel button.

After login, the login information on the page

There is a logout button on the page

Processing of login timeout

two。 Switching between foreground and background of application

1) App switches to the backend, and then goes back to App to check whether it stays in the previous interface.

2) App switches to the backend, and then returns to App to check whether the function and application status are normal.

3) when App switches to the background and returns to the foreground, pay attention to whether the program crashes and whether the functional status is normal, especially when the data is automatically updated when switching back to the foreground from the background.

4) enter the App after unlocking the phone screen to see if it will crash and whether the function status is normal, especially when the data is automatically updated when switching from the background to the foreground.

5) when a phone call is interrupted during the use of App, and then switch to App, whether the function status is normal.

6) when the App process is killed, whether the App,App can be started normally.

7) after the prompt box that must be dealt with appears, switch to the background, and then switch back to check whether the prompt box still exists, sometimes there will be defects that the application skips the prompt box automatically.

8) for pages with data exchange, each page must be tested for switching between foreground and background and locking the screen, and this kind of page is most prone to crash.

3. Landing limitation

Many applications provide login-free features that automatically use App as the user who logged in last time when the application is opened.

1) consider whether you can enter login-free status normally when there is no network.

2) after the switching user logs in, check whether the user login information and data content are updated accordingly to ensure that the original user exits.

3) according to the existing rules of Mtop, only one machine is allowed to log on to an account. Therefore, you need to check how many phones are logged on to one account. Users in the original phone need to be exited and give friendly hints.

4) App switches to the background and switches back to the foreground for verification.

5) switch to the background, and then switch back to the foreground test.

6) after the password is changed, check whether the valid identity is verified when there is data exchange.

7) applications that support automatic login check whether the system can log in successfully and the data operation is correct when performing data verification.

8) after checking that the user logs out actively, the next time you start App, you should stay in the login interface.

4. Offline browsing

Many applications will support offline browsing, that is, some of the data will be cached on the local client for users to view.

1) in the case of wireless network, you can browse local data.

2) you can browse normally when you exit App and open App.

3) switch to the background and then go back to the foreground to browse normally.

4) unlock the screen and unlock it back to the application foreground to browse normally.

5) give offline prompts when there are updates to the data of the server segment.

5.App update

1) when the client has a new version, there is an update prompt.

2) when the version is an unforced upgrade version, the user can cancel the update, and the old version can be used normally. The next time the user starts App, the update prompt still appears.

3) when the version is a mandatory upgrade version, but if the user does not make an update after the mandatory update, exit the client. The next time you start App, you will still be prompted for a forced upgrade.

4) when the client has a new version, if the client is not deleted locally, directly update to check whether it can be updated normally.

5) when the client has a new version, check whether the updated client function is a new version without deleting the client locally.

6) when the client has a new version, check whether the resource files with the same name, such as images, can be updated to the latest version without deleting the client locally. If the above can not be updated successfully, it is also a defect.

6. Positioning, camera service

1) App is useful for cameras. When positioning services, you need to pay attention to the differences in system versions.

2) where the camera service is useful, you need to test the switching between the front and background to check whether the application is normal.

3) when testing the camera service, you need to use a real machine for testing.

7.PUSH test

1) check whether Push messages are sent according to the specified business rules.

2) when checking that the push message is not received, the user will not receive the Push message.

3) if the user sets a do not disturb period, check that the user does not receive Push during the do not disturb period. During the non-do not disturb period, the user can receive the Push normally.

4) when the Push message is aimed at the logged-in user, you need to check whether the received Push matches the user's identity, and push other people's messages without error. In general, only the message is pushed to the last logged-in user on the phone.

5) when testing Push, you need to use a real machine for testing.

Fifth, performance testing:

1) response ability test: test whether all kinds of operations in App meet the requirements of user response time.

Response time for App installation and uninstallation

Response time of various functional operations of App

2) stress test, whether the system resources are occupied abnormally under repeated / long-term operation.

App repeatedly installs and uninstalls to check whether the system resources are normal.

Other functions operate repeatedly to check whether the system resources are normal.

VI. Cross event testing:

A testing method is proposed for the service level division and real-time characteristics of intelligent terminal applications. Cross-testing, also known as event or conflict testing, refers to a test in which a function is being executed while another event or operation interferes with the process. Such as: App in the foreground / background running status and incoming calls, file downloads, music listening and other key applications of the interaction test.

Cross-event testing is very important to discover potential performance problems in many applications.

1) whether running multiple App at the same time affects the normal function.

2) whether the front / background switch of App runtime affects the normal function.

3) make / receive calls while App is running.

4) App runtime sends / receives information.

5) send / receive mail when App is running.

6) browsing the web while App is running.

7) App runtime uses Bluetooth to send / receive data.

8) App uses cameras, calculators and other mobile devices when it is running.

7. Compatibility testing:

Main test for internal and external compatibility

1) compatibility with local and mainstream App

2) whether it is compatible with various devices. If there is cross-system support, it is necessary to check whether the behavior is consistent under a single system.

Compatibility of different screen marking rates of mobile phones

Compatibility of different mobile phone brands

8. Regression test:

1) regression testing is required after the Bug is repaired and after the new version is released.

2) regression testing after Bug repair requires regression testing of a large number of use cases before delivery.

IX. User experience testing:

From the perspective of subjective ordinary consumers to perceive the comfort, usefulness, ease of use and friendliness of products or services. Through different individuals, independent space and non-empirical statistical reuse to effectively evaluate the experience characteristics of the product, and put forward suggestions to improve the potential customer satisfaction of the product.

1) whether the data interface design is available to guide the user to perform the operation.

2) whether or not to abuse user guidance.

3) whether there are unclickable effects, such as: your button is not available at this time, then be sure to gray out, or remove the button, otherwise it will mislead the user.

4) whether the menu level is too deep.

5) whether there are too many branches of the interactive process.

6) whether the relevant options are far away.

7) whether to load too much data at a time.

8) whether the clickable range of the button in the interface is moderate.

9) whether the tab is not dependent on the content, when the tag is switched, the content is switched.

10) the operation should have a primary and secondary subordinate relationship.

11) whether to define the logic of Back. When it comes to software and hardware interaction, the back key should be specifically defined.

12) whether there is a design of horizontal screen mode, applications generally need to support horizontal screen mode, that is, adaptive design.

Gesture operation test:

1) the influence of the mobile phone unlocking screen on the running App.

2) the influence of switching between foreground and background of running App.

3) switching between multiple running App.

4) shut down the App when it is running.

5) restart the system while App is running.

6) charging while App is running

7) when App is running, Kill drops the process and then opens it.

11. Client database test:

1) General add, delete, change, check and test.

2) whether the table can be created automatically when the table does not exist, whether it can be built by itself after the database table is deleted, and whether the data can be automatically obtained from the server and saved.

3) when the business needs to retrieve data from the server and save it to the client, whether the client can save the data locally.

4) when the business needs to fetch data from the client, check whether the App data can be automatically extracted from the client data, or will it still be obtained from the server? Check whether App data can be automatically obtained from the server side and saved to the server side when the client data does not exist.

5) whether there will be corresponding updates on the client and server when the data is modified or deleted by the business.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.