Mobile APP testing is mainly aimed at the two mainstream operating systems of android and ios, and the main considerations are functionality, compatibility, stability, ease of use (that is, human-computer interaction), performance and so on.
Android and IOS system
>>Operating Mechanism
The Android system is an intelligent and open software platform developed and distributed by Google with Linux as the core. Its applications are generally written in Java. The operating mechanism of the Android system mainly uses a virtual machine, and the system needs to occupy a large amount of memory in exchange for execution speed, plus an irregular automatic memory recovery mechanism. Therefore, mobile phone users using the Android system often feel that their mobile phones are stuck.
The IOS system is a closed mobile phone operating system launched by Apple in January 2007, and its main development language is Objective-C language. Because its operating mechanism is mainly a sandbox, and no virtual machine is required during the entire operation process, its execution efficiency is higher than that of the Android system.
Preparation before mobile APP test
1. Use the same type of product, not just use, but test the same type of product.
2. Familiar with the spec documents of our products, actively communicate with PM.
3. Write test cases.
Key points of mobile APP testing
Functional test (process test, function point test), compatibility test, cross test, installation and uninstallation test (including application upgrade), stress test (interface stress test).
Functional test: Test the specific function points one by one to ensure that each point can correctly realize the corresponding function. For example, starting and running, registering and logging in, switching between front and back, the most common problems are special symbols, boundary values, buttons and the like.
UI Testing: UI testing is also known as user interface testing. Whether the text prompts are friendly, whether there are sensitive words, keywords, etc.; whether the operation is simple and user-friendly, whether there are helpful guidance; adaptive interface design, whether the content is adaptively adjusted according to the size of the window; whether the pictures involve copyright, privacy, patents And other issues.
Compatibility test: Test the installed applications of mainstream devices in the market to ensure that they can run normally; in terms of compatibility, the version, model, and resolution of the mobile phone are considered. There are differences between different versions, and generally low versions are prone to problems.
Stability test: mainly crashes, system crashes, unresponsive and the like.
Performance test: It is mainly realized by tools, such as CPU usage, memory usage, battery temperature, etc.
Security testing: user security, including whether there is a risk of deducting fees when the user makes a call, sends a text message, or connects to the network; whether the user password is encrypted during transmission; when the user logs out of the account, whether the interface that requires authentication can be called, etc. ;Data security: whether the user's sensitive data is written to the log or configuration file; when the user uses sensitive data, whether to prompt the user or a security warning; whether to carry out legal verification of the digital certificate for secure communication, etc.; Communication security: all mobile phone functions should be prioritized, such as answering calls, receiving text messages, etc.; when the network is interrupted or abnormal, users need to be reminded of network abnormalities, etc.
Installation and uninstallation test: ensure that the application can be installed, uninstalled, and run correctly (note the application's upgrade test: the state before and after the upgrade);
Stress testing: applications with a large number of users and high interactivity need to perform stress tests on the interface to ensure that the application can run normally under the condition of a large number of users.
Weak network test: Detect the response of the App's business operations in the corresponding network environment, mainly to simulate the weak network environment for bandwidth, packet loss, delay, etc.
Points to note when functional testing
1. Login
●When the login user name and password are wrong, there will be a prompt message on the interface
●After the user voluntarily logs out, the next time the APP is started, it should enter the login interface
●For APPs that support automatic login, whether the automatic login is successful and the database operation is correct during data exchange
●After the password is changed, whether the verification of valid data has been done when logging in
●Whether to control the operation of some pages when not logged in
●Switch account login, check whether the login information is updated in time
●When operating on multiple ends, ensure that the database operation is correct, and each end can see the data update in time
●For some software, one account is only allowed to log in to one machine. At this time, it is necessary to check whether the original user is removed when the account logs in to multiple mobile phones, and a prompt message can be given
2. Offline
Offline means that the local client of the application will cache some data for the next call of the program
●For some programs, after logging in, local data can be browsed when there is no network
●When there is no network, when refreshing to obtain new data, the data cannot be obtained and a friendly prompt can be given
●Switch to the background and switch to the foreground again, you can view it normally
●Connecting to the Internet after being offline, when the data is updated at this time, it is necessary to obtain new data from the server to update the client data, and to update the local cache information
●Offline viewing is not available for data on some interfaces, and corresponding prompts need to be given and there is no data after the interface is updated
3. Database
Both the android and IOS clients use the database.
When APPs need to save data on the client side, they will create corresponding database tables. The most common one is to save the account. At this time, the test points mainly include:
●Like a general database, it is necessary to check the addition, deletion, modification and query of data
●The client is ready-to-use and built. When the table does not exist, whether it will be automatically created
●After the data table is deleted, can the data in the newly created table be automatically retrieved from the server and saved
●When the data is modified or deleted, can the client and server be updated accordingly
● Get data, whether the client gets it directly from the client or compares it with the data on the server
● For the data updated by the client from the server, whether the client saves it locally.
Finally: The complete software testing video tutorial below has been sorted out and uploaded, and friends who need it can get it by themselves [Guaranteed 100% free]
Software Testing Interview Documentation
We must study to find a high-paying job. The following interview questions are the latest interview materials from first-tier Internet companies such as Ali, Tencent, and Byte, and some Byte bosses have given authoritative answers. Finish this set The interview materials believe that everyone can find a satisfactory job.
