Chapter IX app project test (the end of this chapter)

9.4.5  Fiddler

It's a HTTP Debugging agent tool for , It works as a code server , Monitoring system HTTP network data , It is commonly known as bag grabbing tool . You can directly go to the official website to download and install

1、Fiddler Tool is introduced

start-up Fiddler after , Enter start Fiddler Main interface , Pictured 9-13 Shown

Briefly introduce the meaning of each field in the interface , See table 9-4

 

2、Fiddler Grab interface

（1） To configure Fiddler

First start Fiddler, Click... On the launch page  Tools"-"Options", Pictured 9-14 Shown , In the pop-up Options On the page , single click “Connections" Options , Check ”Allow remote computers to com-nect" Click again "OK" Button , Pictured 9-15 Shown .

（2） Configure mobile phone

First, set up your phone  （vivo For example ) Enter developer mode , Mobile phone “ Set up ”- About mobile phone - Click on the straight “ Software version number ” Prompt appears “ You are already in developer mode “ Pictured 9-16 Shown .

Then enter “ Developer options ”- Enable "USB” debugging , Pictured 9-17 Shown .

 

  Finally, enter the mobile phone “ Set up ”- choice “Wlan” choice Wifi- Go to advanced settings options - Select Manual proxy , take “ Proxy host name “ Change to connect to the mobile computer IP Address ””, Change the port to 8888

（3） Grab HTTP Interface

start-up Fiddler And mobile phones APP Program , Can be in Fiddler The mobile phone request data and response data can be seen on the interface , Pictured 9-18 Shown . The parameters of the interface can be found in JSON View in .

3、Fiddler Analog weak network

 Fiddler It also provides a network speed limit function , Provide network speed limit , It can simulate some real environments of users, that is, the environment of weak network APP test .Fiddler Analog weak network needs to set delay time . Algorithm for ： Time to delay （ millisecond ）=8*1000/ Network speed . For example, simulation 2G The network uplink speed is 2.7KB/s, The downward speed is 9.6KB/s) The speed of , The calculation method is as follows ： The uplink delay is 8*1000/2.7=2962ms, The downlink delay is 8*1000/9.6=833ms

stay Fiddler The specific setting steps are as follows ：

First start Fiddler In the menu bar Rules Next - single click “Customize Rules" Options , Pictured 9-19 Shown .

In the pop-up  “Fiddler Script Editor” On the page , Search for “m Simulate Modem" Field , Then modify the following 2 Row data , Pictured 9-20 Shown .

 oSession["request-trickle-delay"]="300"; Medium 300 Change it to 2962
oSession["request-trickle-delay"]="150"; Medium 150 Change it to 833 preservation

Finally, after modifying the delay , stay Fiddler In the interface , choice "Rules"-“performances"-"Simulate Modem Speeds", Check this item , Pictured 9-21 Shown .

Here we are Fiddler Weak network setting is completed . 

9.5 APP Test and Web Test differences

Whether it's APP test , still Web test , Relative to testing , Its testing process 、 There is no big difference in the test ideas , Because of the test environment 、 The tools are different 、 The method of testing is slightly different . The main differences are summarized as follows

1、 The system architecture is different

Web The project is mainly browser based B/S framework , When Web After the server updates , The client will update synchronously . and App After the server updates , If the updated version is forced update , The mobile terminal must be updated , Otherwise, the function cannot be used ; If the updated version is not mandatory , At this time, deal with the new version of the test , Also test whether the core functions of the old version are affected .

2、 The test method is different

1） A functional test ： The idea of testing is to test the six characteristics of software quality one by one , The only difference is Web The project does not support offline browsing , There are some APP Support offline browsing , When the network is available, the data will be updated synchronously .

2） Performance testing :Web The main focus of the project is on the pressure of the server and Web Page response , and APP In addition to considering the pressure on the server side , We also need to consider the performance of the mobile phone , The main problem is memory usage .

3） Compatibility test ：Web The project mainly considers browser compatibility , and APP The project needs to consider different equipment 、 Different systems 、 Versions of different systems 、 Different resolutions, etc 、

4） Special tests ： relative Web test , stay APP Some special tests are added to the test , E.g. power test 、 Weak network test 、 Install the uninstall 、 Upgrade update 、 Terminal test 、 Access test, user experience test, etc .

3、 Testing tools are different

Automated test tool ：APP In general use Monkey、Runner and Appium; and Web The end is generally used QTP and Selenium.

Performance testing tools ：APP In general use HyperPacer、Monkey、Jmeter、Loadrunner12.0; and Web The end is generally used Jmeter and Loadrunner、
Weak network testing tools ：Fiddler、Network、Link Conditioner(IOS)

9.6 H5 Test page

It is a hypertext markup language （HTML） The fifth major revision of , abbreviation H5.HTML5 Is designed to support multimedia on mobile devices , It also introduces new features , Can really change the way users interact with files . So it's going on H5 The test needs to pay attention to the following points ：

1、 Function related

1） Pay attention to whether the request of each page is correct , Is there any repetition

2） Focus on APP cache , Whether the function is correct after clearing the cache , Whether there is a retry mechanism after data acquisition failure .

3） Focus on logging in H5 And Native Switch

4） Pay attention to the loading and refreshing of the page

5） Focus on network issues , Especially weak networks and switching between networks , Yes H5 Does the page have any effect

6） Pay attention to the background page switching in front of the page

7） Focus on mtop Interface processing

2、 Performance related

1） Pay attention to the loading time of each page 、 Size and number of requests .

2） Pay attention to the response of the page under the weak network

3） Whether to add local cache properly

3、H5 adapter

1） Pay attention to browsers of different brands of mobile phones

2） Pay attention to the screen size and resolution of different brands of mobile phones .