http://bbs.51testing.com/thread-1159778-1-1.html
1. Technically :
WEB testing and mobile terminal testing are basically similar in testing type, and they all need to perform functional testing, performance testing, security testing, GUI testing and other testing types.
Their main difference lies in the details and methods of specific tests.
Web projects are generally b / s architecture, browser-based, while app is c / s, there is a client.
2. From the perspective of system architecture :
As long as the web test is updated on the server side, the client will be updated synchronously;
and if the server is modified under the app, it means that the core version used by the client user needs to be regression tested again .
3. Client performance : The
web page may only focus on response time, and the
app also needs to care about traffic, power, CPU, GPU, and memory.
4. compatible aspects :
Web is a browser-based, so the more likely a browser (IE, chrome, Firefox) and computer hardware, computer
compatible with the direction of the system;
App test must rely on a cell phone or pad, not only depends on resolution Rate, screen size, important to see the equipment system
5. The special test of the app :
1) Multi-network test : wireless network, 2G, 3G, 4G, etc., network disconnection, poor network speed and page display when switching between networks, etc. In addition, under non-wifi, also Need to pay attention to network usage issues
2) Interruption test : such as phone calls, SMS, notifications, power outages, etc., the software needs to deal with these special cases
3) Installation test : In addition to the conventional user data processing during installation, update, and uninstallation, it must also be considered To unusual scenes. Including interruption during installation, weak network, deleting installation files after installation, incremental package update, breakpoint resuming; reminder mechanism for upgrade test, whether the cancellation of upgrade will affect the use of original functions, and whether user data is cleared after upgrade
4 ) Interface test : For example, the display of pictures with different sizes and specifications on different screens; for touch screen mobile phones, you should also pay attention to gestures, horizontal and vertical screen switching, multi-touch, etc.
5) Weak network test : you need to test the weak network The user experience can be considered from several dimensions such as function, performance, exception handling, and scene characteristics.
Function: Under the weak network, do functional test, not only the sub-performance test, but also a kind of reliability test
Performance: Test the response time of the app from the hot start of the app, page switching, front and background switching. In particular, the H5 page needs to test the first screen time, whether there is a 302 jump, page size, etc., otherwise there will be various white screens, splash screens, chrysanthemums, etc. In addition, the overall time of the API request, response and body size can be inferred through the network to infer whether the server is processing slowly, or the transmission packet needs to be managed; if the time is small, the body is small, and it is still very slow, this is the problem of the client program .
Strong network form scenarios: some scenarios must be done with wifi turned on; for example, WeChat upgrades will monitor whether the user is plugged in and connected to wifi. Once monitored, the upgrade can be notified.
Fault tolerance mechanism: Mainly consider the instability brought by the weak network situation, wait for timeout ANR, or directly flash back abnormally. The processing of these must be elegant, so the copy of the abnormal information must be beautiful
Reconnection mechanism: involves two blocks, one is whether the client will resend the request, and the other is whether the server accepts the reconnection. In conjunction with the timeout mechanism, how long will it take to initiate a reconnection without feedback, and failure will not be allowed to reconnect
No-network state test: first, the page is displayed without the network; secondly, data integrity and session consistency; in addition, it is also necessary to pay attention to whether the network will continue to request the network and continue to perform network-related operations. Will there be any accumulation of requests when recovering from no network to a network?
https://blog.csdn.net/dushu990/article/details/53302246
1. Record bugs
On the Web side, you can use the system's own screenshots and QQ screenshots to capture the pictures of the bug. For the errors, you can use the tool's own logo to focus on the mark.
For mobile devices, you can use the screenshot tool that comes with the mobile phone to take a screenshot and then transfer it to the computer. You can use the "transfer file / photo to computer" function of the mobile phone QQ. There is also a more convenient way to connect the mobile phone to the computer with a data cable, use a third-party tool to synchronize the mobile phone screen in real time, and use the screenshot tool on the PC side to take screenshots of the page with bugs.
When reporting many mobile bugs, you need to attach the relevant log, record the test environment, mobile version, etc.
2. Test environment
The test environment on the Web side is often switched by hosts. The switchhosts tool can easily switch the required hosts, but the mobile terminal is more complicated to set up. The simpler way is to set the proxy on the computer and connect the proxy directly on the mobile terminal. Note that the phone and computer must be connected to the same network.
It is recommended to use Fiddle to set the proxy, which can capture data packets on the mobile phone.
3. Compatibility
Web-side testing generally uses a browser, and when the system is basically stable, then go to test browser compatibility.
However, for the mobile terminal, this method does not work, because the mobile terminal is mainly divided into Android and IOS, and the problems that occur at these two ends are generally inconsistent. The problem of consistency is mainly data problems. It is processed in the background, so we need to focus on testing at both ends when testing, without the problem of focusing on testing one end first.
Note: The general method is to test one end, if there is a problem, immediately see if the other end also has this problem.
4. Characteristics of mobile terminal
Comparing the mobile terminal and the web terminal, the mobile terminal has many characteristics:
①Multiple network types The
mobile terminal has multiple networks: wireless network, 2G, 3G, 4G, etc. The display of the page at the time of switching is very important for the mobile terminal. In addition, under non-wifi, you also need to pay attention to network usage.
②Intermittent problem The
mobile terminal has a very important problem. Generally, the process of using the software is not long. Many interruptions may occur in the middle, such as phone calls, text messages, notifications, power outages, etc., the software needs to deal with these special Happening.
Open a page, or during the operation (after clicking a button), lock the screen of the phone, and when it is opened again, can the application process normally.
③Restrictions on the screen Display of
pictures and text; whether the display of uploaded different picture sizes is normal; how is the effect when pictures and text are displayed together.
Operation area; web-side applications are generally not limited by the screen, and are more accurate by mouse operation. However, due to the small screen and large size of the mobile terminal, the pages and buttons will be limited by the screen size. In addition, users are operating with their fingers. Are some buttons, selection boxes, etc. easy to click, and multiple clickable areas are located closer When the click position is slightly offset, it may cause different results. In this case, whether the pre-effect can be achieved.
④ The software starts and runs. The
mobile terminal starts, uninstalls, and upgrades. This is relatively common and important. For example, what to do when the user's data is upgraded, how to handle the user's data after uninstalling, and uninstalling and installing the user login data display Wait.
⑤ The gesture
mobile terminal also has a major feature. Some mobile terminals support custom gestures. Users can perform an operation through gestures, such as left swipe to delete, right swipe to return to the previous page, and left and right slide pictures. The software needs to perform this gesture. adaptation.
⑥ Sharing The
mobile terminal is usually equipped with a lot of software. When the user places an order or the product has activities, the user will share it. However, the sharing permissions and whether there are software problems require special treatment and testing. General software or applications will open a part of the page, allowing users to access it without logging in. Some pages require the user to log in, mainly to share these two pages with different permissions, and then enter this page through sharing to view Whether the control of authority is normal.
⑦ Synchronization of web and mobile
Whether the user's operation on the web can be synchronized and displayed normally on the mobile; the operation on the mobile, whether the user logs in to the web account and whether the information is synchronized, etc.