Summary of wechat applet test points

Catalog

Preface

One 、 Authority test

Two 、 A functional test

3、 ... and 、 The interface test

Four 、UI test

5、 ... and 、 Ease of use test

6、 ... and 、 Network testing

7、 ... and 、 Compatibility test

8、 ... and 、 Version configuration test

Nine 、 Performance testing

Ten 、 Cache test

11、 ... and 、 Embedded point test of applet

---

Preface

The applet is developed by wechat and does not need to be downloaded and installed , Applications that need to be reviewed by wechat on-line . The version types of applet products are divided into ： Development Edition 、 Experience version 、 Official version . Development Edition 、 The experience version does not need to be reviewed , Just give the micro signal permission , After scanning the QR code of the applet, you can access . At the level of simple functional testing , Wechat applet test 、APP test 、web There is no difference between process and functional testing , But due to different carriers , It leads to some differences .

Generally speaking, from 11 Test three aspects ： Authority test 、 A functional test 、 The interface test 、 Performance testing 、 Compatibility test 、 Ease of use test 、UI test 、 Network testing 、 Version configuration test 、 Cache test and buried point test etc. 11 Introduce every aspect .

One 、 Authority test

Development Edition 、 Experience version Wechat audit is not required , You only need to give permission to the test micro signal , You can access... By scanning the QR code of the applet ; The official version needs wechat review , If you need to log in after review , You need to give login permission to the micro signal .

The test function points of the small program wechat authorization are roughly as follows ：

• Allow the authorized , Go to the next step ;

• Deny authorization , Can't operate next ;

• Close exit , If you re-enter without authorization, you need to continue Authorization ;

• Close exit , If authorized, there is no need to authorize again ;

• Log in to the applet after replacing the wechat login device , You need to re authorize the applet ;

• After the same micro signal is authorized to log in to the same applet at different mobile wechat terminals , The data that can be viewed and the permissions of operations should be synchronized .

                   

 

Two 、 A functional test

1、 Test according to function module

The functional modules of each category designed by the module are divided , Then subdivide it step by step , Cover every functional test point as comprehensive as possible .

2、 Test by business process

1） Applet business , such as ： Play 、 payment （ Pay attention to the payment status ： Single authorization ？ Unclassified ？）;

2） Connect various function points to form a complete business process to check ;

3） The same salesman , There are different paths to achieve , Each path needs an override check .

3、 Test by data flow

1） Operate input and output flows from one end according to data , Design test cases based on data flow , The output data may also become the input at the other end ;

2） Check whether the input data performs the correct output according to the code logic ;

3） Whether the data is abnormal , Unable to input 、 There are inputs but no outputs 、 Incorrect output 、 Redundant output other information, etc ;

4、 Check and test the effectiveness of different entrances with the same function

1） The applet is on the home page 、 List of pp. 、 Detail page 、 Other business function related pages , There may be an entrance to the same function ;

2） Each entry path needs to be overridden ;

5、 Interactivity check test

1） generally speaking , There are several categories of data and function interaction changes ： Between the front desk and the front desk 、 Between the front desk and the back desk 、 Between backstage and backstage ;

2） Front desk from F1 The data submitted by the page , May need to be at the front desk F2 Page view to , It will also be in the corresponding background B Page found record ;

3） backstage B1 Data modified or added to the page , Corresponding to the front desk F The page changes interactively , The output value of the same data may also exist between different pages of the background itself ;

6、 Payment test

1） Payment status at the time of payment ： Single authorization 、 Unclassified ;

2） Whether payment can be made after releasing the secret free Authorization ;

3） There is an amount when paying 、 No amount 、 How to deal with the payment order and so on ;

4） How are unpaid orders handled ;

5） The applet is not authorized to pay , How does the applet handle ;

3、 ... and 、 The interface test

1） With interface documentation , Refer to the interface document for interface test .

2） No interface documentation , Use Charles or fiddler Grab the bag ( Same as app Grab the bag )

Interface testing is not described in detail here .

Four 、UI test

1）  Page interaction ;

2） Page presentation elements ： Check the interface aesthetics of the applet 、 font size 、 Font format 、 Button layout, etc .

               

 

5、 ... and 、 Ease of use test

1、 Navigation

1） Navigate to the location of a module on the page ;

2） Go back to the top or bottom ;

3） Expansion of navigation bar ;

4） Whether the text of the navigation label is easy to understand ;

5） Fail after the maximum number of page jumps exceeds the limit （ The native page of the applet exists 10 Layer restriction problem , exceed 10 Layer cannot open a new page , When the business process or access forms a closed loop, it is easy to fall into 10 Layer problem ）.

2、 Function entry

1） The function entry of repeated and commonly used business ;

2） Whether it is in a prominent position ;

3） Whether the business operation is easy for most users to use and view .

3、 Upper and lower layers enter and return

1） Between the first page and the list page ;

2） Between list page and detail page ;

3） Between the front page and the detailed page ;

4） Whether the entry and return between different levels have corresponding keys for easy operation ;

4、 typeface 、 picture 、 Dynamic interaction effects

1） typeface ： label 、 title 、 Content 、 Play fonts dynamically ;

2） picture ： Background map 、 Shuffling figure 、 Interaction diagram generated by touch screen ;

3） Whether the operation is too cumbersome .

6、 ... and 、 Network testing

1、 Network switching test

1）WIFI Cut to 2G/3G/4G/5G;

2）WIFI Switch to no net ;

3）2G/3G/4G/5G Cut to WIFI;

4）2G/3G/4G/5G Switch to no net ;

5） No net cut to 2G/3G/4G/5G;

6） No net cut to WIFI;

2、 Verify whether it is normal under various network conditions

About the choice of network speed ：

• 3G：300k-2Mbps about

• 2.5G(GPRS) Generally in 100kbps

• 2G（GSM） Generally in 5-9kbps

If you are not used to custom setting bandwidth, etc , Can directly test the gradual increase of network speed . After setting up , You can start your applet for various network tests .

 

7、 ... and 、 Compatibility test

1） Operating system compatibility （Android edition /iOS edition ）;

2） Screen compatibility test （ The screen resolution affects the layout of the page ）;

3） Wechat version compatibility test ;

4） QR code compatible （ Whether the QR code pictures shared to friends or circle of friends can be scanned correctly ）

8、 ... and 、 Version configuration test

For different templates , Modify the corresponding... In the front-end program code Configuration parameters , Switch between versions .

1、 Non public parts

Direct switching between different versions , It is necessary to ensure that the functional modules and data independence of each other are not disturbed , That is, the data added in the background of different versions of management should only be called into the foreground applet of each corresponding template , The data submitted by different versions of applets from the foreground will only be submitted to their respective management background .

2、 Common parts

Switch between different versions , The same function module and public data information will be displayed .

Nine 、 Performance testing

1） White screen time of the page ;

2） First screen time ;

3） Resource occupation ;

4） Page rendering time

Ten 、 Cache test

User local cache （ Applet file 、 Authorization data 、 Login data, etc ） No more than 10MB, The function of cache is to improve the fluency of the program 、 Reduce network requests 、 Save server resources , Its cache test point ： Whether to force exit when clearing the cache 、 Background cleaning and shutdown , Every time you submit or exit , Whether to clear the cache of this form .

11、 ... and 、 Embedded point test of applet

The embedded point test of small program is basically the same as that of other end processes ： The products put forward the demand for embedded points , Developers configure buried point events on the platform , Then the code is buried , The tester then tests the buried point .

Be careful ： The pit often encountered in the process of small program testing ： Level page Jump 、 Compatibility 、 cache .