Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

Analysis of key points of Mobile phone App Test

2025-04-07 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Internet Technology >

Share

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

Preparation before APP test for a mobile phone:

Mobile phone APP testing is mainly aimed at the two mainstream operating systems, android and ios, and mainly considers functionality, compatibility, stability, ease of use (that is, human-computer interaction) and performance.

Preparation before test: 1. To use the same type of product, not only to use, but to test the same type of product. two。 Be familiar with the spec documents of our products and actively communicate with pm. 3, write test cases, there is no time to have at least one checklist.

2. Key points of APP testing for mobile phones:

Functional test (process test, function point test), compatibility test, cross test, installation and uninstall test (including application upgrade), stress test (interface pressure test)

Functional testing: test the specific functional points one by one to ensure that each point can correctly achieve the corresponding function; functional aspects have not yet reached the level of automation in the market, mainly by manual testing. The ones with the most problems are special symbols, boundary values, buttons and so on. Basic functions, mainly refers to whether the app has completed all the functions of the design. Distinguish the modules and write a checklist to avoid missing the test. Consider switching between landscape and portrait screens, but many app currently only support portrait screens.

Compatibility testing: perform tests on the mainstream equipment installation applications in the market to ensure that they all work properly; the version, model and resolution of the phone are considered in terms of compatibility. There are differences between different versions, and generally lower versions are prone to problems.

Stability testing: mainly flicker, system crash, no response and so on.

Usability testing: consider whether the interface is attractive, easy to understand, clean, simple, and typos-free. Click to determine the scope and so on. In this part of the test, the requirement bug is usually submitted if the test finds something unreasonable.

Performance testing: mainly rely on tools to achieve CPU footprint, memory footprint, battery temperature and so on.

Cross-testing: for running applications, if you enter the response of SMS, phone and other software, it will not affect the tested application, and will ensure that the application can run correctly. The main considerations include SMS interference, low power reminder, push reminder, usb cable plug reminder, charging reminder, etc.

Installation and uninstall testing: ensure that applications are installed, uninstalled, and run correctly (pay attention to application upgrade testing: status before and after upgrade)

Stress testing: applications with a large number of users and high interaction need to perform stress tests on the interface to ensure that the applications will not run normally in the case of a large number of users.

Outfield: network switching, app operation in the case of strong and weak network signals.

Matters needing attention:

Flashback (insufficient memory, etc.). On mobile phones, this kind of problem is very likely to occur, so you should focus on testing, for example, returning to access a module (the module that data is always obtained), switching applications, repeated submission, incoming call interaction and so on are the reasons for the high rate of flashback.

Here are some points to pay attention to during functional testing:

1. Log in

When the ● login user name and password are incorrect, the interface has a message.

After ● users actively log out, the next time they start APP, they should enter the login interface.

● for APP that supports automatic login, whether the automatic login is successful and the database operation is correct when exchanging data.

After the ● password is changed, whether the valid data is checked when logging in.

Does ● control the operation of some pages when not logged in?

● switches accounts to log in to verify that the login information is updated in a timely manner

When ● operates on multiple sides, it ensures that the database operations are correct and that each side can see the data updates in time.

For some software, ● supports that one account is only allowed to log in to one machine. In this case, you need to check whether the original user is removed when the account logs in to multiple phones, and can give prompts.

When ● APP switches to the background, switch to the foreground test again. For example, when logging in, a phone call comes in.

2. Offline

Offline is that the application caches part of the data on the local client so that the next call of the program

● for some programs, after logging in, you can browse local data without a network.

When ● does not have a network, when refreshing to get new data, it cannot get data and can give friendly prompts.

● switches to the background, and when you switch to the foreground again, you can view it normally.

When ● is offline and connected to the Internet, when there is an update to the data, you need to obtain new data from the server to update the client data, and update the local cache information.

● does not provide offline view of the data in some interfaces, so you need to give the corresponding prompt and there is no data after the interface update.

3. Database

Both android and IOS clients use databases

When APP needs to save data on the client, they will create corresponding database tables. The most common thing is to save the account. The main test points at this time are:

Like general databases, ● needs to check the addition, deletion, modification and query of data.

Will the ● client be created automatically when the table does not exist?

After the ● data table is deleted, can the data in the newly created table be automatically obtained from the server and saved?

●, when the data is modified or deleted, can the client and server be updated accordingly?

● acquires data, and whether the client obtains the data directly from the client or compares it with the server-side data

● whether the data updated by the client from the server is saved locally.

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.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Internet Technology

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report