Mobile Internet Testing

<span id="Label3"></p>1 Mobile Internet Overview<p><p>Mobile Internet is the combination of mobile communications and the Internet. Refers to the Internet's technology, platforms, business models and applications and mobile communication technology combined with the practice of the collective Name. Compared with this is the traditional internet, the traditional internet and mobile Internet are the categories of the internet, if you want to say the difference between the mobile internet and the traditional internet, it is "mobile." Now the "mobile" feature is embodied in "anytime" and "anywhere" to use the network to obtain the required Information.</p></p><p><p>In the early days of the development of mobile internet, the interface and interaction of most products were designed according to the experience gained during the Internet period of production Pain. however, in the process of slow experience, it is found that the experience of these experiences on the mobile platform is more and more popular, so it is necessary to design the mobile Internet according to the characteristics of mobile internet.</p></p>2 The difference between mobile Internet and traditional connected experience<p><p>As a mobile internet test engineer, need to have good experience in the use of products, and these experience will lead you to test the product, only a full understanding of the characteristics of mobile Internet will be able to do the test, the product to the Extreme.</p></p>2.1 User Focus Points<p><p>The early internet, the user through the Web page, because the computer screen is relatively large, so need to obtain more information, rather than to the user through a large number of clicks, page to get enough Information.</p></p><p><p>And the mobile Internet terminal, the largest is the pad computer, but only a 10-inch screen large, most of the 4-inch ~5.5-inch screen, this time if still on such a large page display dense information, will eventually lead to users will directly throw your Company's products into the garbage basket! A huge challenge for mobile internet is to move from a computer screen to a small screen, to display information that is very limited and valuable, so that designers need to put the best value information in a prominent place in the application, otherwise they will be eliminated.</p></p>2.2 Field Complex<p><p>Traditional internet people generally in the home or office and other fixed places to use computers, I believe almost no one to take the bus and open this computer to look at the Web. But for the mobile internet, more users will choose to use the mobile phone in transit, subway, toilet, Queue. therefore, as a tester, a variety of different scenarios are required to test the product, including network 2G, 3G, 4G, Poor network condition, low power, and other Scenarios.</p></p>2.3 Fragmentation of time<p><p>Most of the time users use mobile apps are fragmented, looking at tweets, watching news, playing games, and More. Then the application needs to be designed with the use of user fragmentation in mind to be able to articulate the uniqueness of the application in a fragmented time, because the user does not have that much time to Waste.</p></p>2.4 Difficulty of input<p><p>Users in the use of the computer, the mouse, keyboard are very convenient input devices. But on the mobile internet, the input of the application becomes more complicated, and the input of mobile Internet is generally divided into physical keyboard and touch Screen. Changes in input patterns can be a temporary non-adaptation, especially in complex interactive scenarios.</p></p>3 Functional Test points 3.1 multi-resolution test<p><p>iOS is now relatively small, thanks to Apple's dedication to delivering the ultimate product to its users. And Android is not the same, from 240*320 to 2560*1600 how big dozens Of. For multi-resolution testing, you might consider using an emulator and a real-computer combination to test it. Android can target Real-world testing based on current market resolution STATISTICS.</p></p>3.2 Multi-System Testing<p><p>The following resolution tests are followed by multi-system-supported Tests. Most Android uses more than 2.3 of the system, relative resolution testing, Multi-System testing is more complex than it, because in addition to the native Android system, many manufacturers in the market has been deeply customized, such as Huawei's emui, millet mui, Meizu flyme, There are other systems for eui, Lenovo's Vibeui and so On. All this adds a certain degree of complexity to the testing effort. The majority of Apple's user base has the habit of keeping up to date with the latest system, and iOS can only be upgraded in one direction, not degraded, making the iOS System's test work relatively simple, but also need to cover as much as 5.0 of the System.</p></p>3.3 User's Different usage habits<p><p><strong>①</strong> <strong>Android</strong> <strong>Permissions Issues</strong></p></p><p><p>As a test engineer, you need to understand what permissions are being used by the object being tested, why it is used, and whether it will cause problems for Users.</p></p><p><p><strong>②</strong> <strong>Android</strong> <strong>Hardware Issues</strong></p></p><p><p>Android Smart Machine systems are emerging, and hardware differences are large. Hardware differences can also cause software vendors to defect, such as physical keyboards and virtual KEYBOARDS.</p></p><p><p><strong>③</strong> <strong>Android</strong> <strong>Operating Habits</strong></p></p><p><p>There are several key buttons: menu key, home key, back key, home button long press, Show List of current processes, adjust volume, standby.</p></p><p><p>The following questions need to be considered: what feedback will be given when clicking the Back button in each interface, when the user clicks the home button in each screen, opens the App's feedback again, whether the app is in the background or the end of the life cycle, or if the app uses the menu key to not omit the case from the App's interaction The system is in standby, after the system is re-awakened, the application is in what state, whether there is correct feedback; if the application process is manually closed by the user, can it be started correctly again.</p></p><p><p><strong>④</strong> <strong>IOS</strong> <strong>Operating Habits</strong></p></p><p><p>There are several key buttons: click the Home button, double click the home button, close the current application, turn volume on or off, adjust volume, standby,</p></p><p><p><strong>⑤</strong> <strong>IOS</strong> <strong>Jailbreak Problem</strong></p></p><p><p>Using different jailbreak tools in the same iOS environment, some of the features of some apps may not behave the Same. Because after the jailbreak, the most common problem is that the system becomes unstable, easy to lead to application conflicts, such as input method, beautify the theme plugin, mobile phone management software.</p></p>3.4 Instability of the network<p><p>The reason why mobile Internet is more spread than traditional internet, popular faster, is because people can take out mobile devices anytime and anywhere to access the internet, such as micro-blog, hair circle, hair space. From the rapid development of the 2G to 4G network, it can be seen that people use the Internet more and more dependent on the Network.</p></p><p><p>The current 3G, 4G signal is not fully covered, some places will appear bad network conditions, this time the application will respond to the User's operation? At this point, test engineers are required to test the application of the response in such scenarios, such as subways, elevators, toilets, buses and other Scenarios. At present, Some applications in this type of prompt are: "network error, Please try again later", this entire tip for users, it is clearly irresponsible practice.</p></p><p><p>The test engineer needs to be completely on the User's side to think about the Problem. For network problems, according to different conditions to give different hints, such as network instability, please try again later, the network is not connected, please reconnect to the network after the attempt, currently unable to receive the relevant data, please try again later ...</p></p><p><p>There is the scene test between the network switch, the network state is changed by the bad Scene Test.</p></p>3.5 Install/uninstall Test<p><p>There are many different ways to install apps for Android and Ios. A variety of third-party mobile phone stewards like android, command-line installation, iOS AppStore and Post-jailbreak pp Helper and other third-party Tools. Although these installation methods are no different from manual command-line installation, it is still necessary for the test engineer to verify the actual operation to ensure the logic of the test point is normal. For Android to support expansion cards, both scenarios need to be tested, and the scenarios where the data is transferred to each other need to be tested.</p></p><p><p>The following scenarios also require attention:</p></p><p><p>I will not be connected to the situation can be normal operation, will not crash?</p></p><p><p>L Online Download data is incomplete, can I start?</p></p><p><p>L support the continuation of the breakpoint?</p></p><p><p>• After successful installation, check the version number and other information</p></p>3.6 Upgrade Test<p><p>App upgrades include incremental upgrades and full-scale upgrades. The so-called incremental upgrade is that the old version of the APK is only 6 m, the new version has 8 m, then the incremental upgrade may only need to download 2M, while the full-scale upgrade is 8M full Download.</p></p><p><p>There are several prerequisites for applying an upgrade: the old and new versions require the same signature; the old and new versions require the same file name; the old and new versions need to have identifiers to differentiate Them.</p></p><p><p>Some other phone ROM will be shipped with some built-in applications, which should be compared with the system's. so files when Upgrading.</p></p>3.7 Concurrency Test<p><p>The difference between app testing and traditional testing is that mobile devices are more concurrent in use, such as when you are using an application, such as incoming calls, text messages, alarms, notifications, Low battery warnings, and so On.</p></p><p><p>What the test engineer needs to test is whether the application can continue to be used without a crash when this happens.</p></p><p><p>Here are a few things to note: the app is playing a video, the app is making a connection to the server or accepting the request, the app is downloading data or upgrading, the user is entering, shutting down or standby, a feature conflict, and so On.</p></p>3.8 Push<p><p>Push functionality is the perfect choice for companies to promote their products and keep users sticky, so push is one of the key Tests.</p></p><p><p>There are a few things to focus on when testing: the ability of the smart machine to perform push functions in the shutdown, standby, and open conditions, the correctness of message display and push jumps, and the ability to apply push-function testing in the case of open or closed situations, application launches in the background, and the success rate of multiple push and push delivery.</p></p>3.9 Share Jump<p><p>A major feature of the mobile Internet is the speed of transmission is very rapid, a news in a very short time can be known, such as micro-bo, QQ space and so On. Scenarios in which sharing successes and failures need to be simulated.</p></p>4 Test Tool Introduction 4.1 Tcpdump/wireshark Introduction<p><p>For tests that need to locate the network Problem-packet loss rate, we can test it using the two tools of tcpdump and Wireshark.</p></p><p><p>Here's How to use It:</p></p><p><p><em>#</em> <em>will be</em> <em>Tcpdump</em> <em>put in</em> <em>Android</em> <em>system in the directory to go</em></p></p><p><p>ADB push <tcpdump Path>/data/local/tcpdump</p></p><p><p><em>#</em> <em>give the appropriate permissions to</em> <em>Tcpdump</em> <em>file directory</em></p></p><p><p>ADB shell chmod 6755/data/local/tcpdump</p></p><p><p><em>#</em> <em>Save the Capture package file</em></p></p><p><p>/data/local/tcpdump-p-vv-s 0-w/data/local/tcpdump/capture.pcap</p></p><p><p><em>#</em> <em>Export Grab Files</em></p></p><p><p>ADB pull/data/local/capture.pcap.</p></p>5 test Case Design<p><p>Scenario: a very common function of a smart machine is to make a phone call, but sometimes it gets a lot of confusing phone calls, so a company captures the point by designing an app with a "blacklist" feature that blocks the number or contact on its list from being able to talk to the owner of the smartphone again. So how do you design test cases?</p></p><p><p>The first thing to think about is the most basic use Case:</p></p><p><p><strong>① add one or more contacts or numbers into the blacklist to block calls</strong></p></p><p><p><strong>② remove one or more contacts or numbers from the blacklist to block calls</strong></p></p><p><p>Both of these use cases should be tested, but experienced testers will come up with new test cases:</p></p><p><p><strong>① when the blacklist does not add any number, the interface is displayed normal</strong></p></p><p><p><strong>② When a number is added to the blacklist, the interface is displayed as normal</strong></p></p><p><p><strong>③ when the blacklist is just full of a screen, the interface shows whether it is normal</strong></p></p><p><p><strong>④ When the blacklist list is more than one screen, the interface is displayed as normal</strong></p></p><p><p>It seems that there are only these use cases, but we imagine the use of this feature scenario, the use of the blacklist function for the following reasons: by a strange number has been harassed, consciously do not want to contact a number, prank, etc.</p></p><p><p>As a result, some test cases are associated with:</p></p><p><p><strong>① add a number directly to the blacklist</strong></p></p><p><p><strong>② Select a contact from a contact to the Blacklist.</strong></p></p><p><p><strong>③ Select a number from the call log to add to the blacklist</strong></p></p><p><p>But it's not enough to tap into the behavior of adding numbers, and you should dig deep into the contact and number two factors:</p></p><p><p><strong>Length of ① number (landline, mobile, short, phs, etc.)</strong></p></p><p><p><strong>② numbers in different ways (E.G.</strong> <strong>13800138000</strong> <strong>and the</strong> <strong>+861380013800</strong> <strong>is a number, including roaming, even multinational numbers, etc.)</strong></p></p><p><p>Is it just these use cases? The answer to You: no! And also.</p></p><p><p>As the current dual-sim, Dual-sim machine, Add a blacklist at this time will produce new use Cases:</p></p><p><p>Dual SIM status (ab has the same number c):</p></p><p><p><strong>① blacklist from</strong> <strong>A</strong> <strong>Card to add</strong> <strong>C</strong> <strong>, with</strong> <strong>C</strong> <strong>Give</strong> <strong>A</strong> <strong>cards,</strong> <strong>B</strong> <strong>cards to call each</strong> other</p></p><p><p>Dual sim case (ab has the same number c):</p></p><p><p><strong>② blacklist from</strong> <strong>A</strong> <strong>Card to add</strong> <strong>C</strong> <strong>, with</strong> <strong>C</strong> <strong>Give</strong> <strong>A</strong> <strong>cards,</strong> <strong>B</strong> <strong>cards to call each</strong> other</p></p><p><p>Mobile Internet Testing</p></p></span>