WeChat applet testing strategy and precautions?

1. Preparation before the test (environment construction)

1. Front-end page

Wechat web developer tool installation, authorization test for micro-signal preview and debug applets

2. Management background

Configure the intranet test server environment, through the output content of the front-end of the PC-side Web site management applet, you can obtain the management account from the developer for testing

2. Test scope

1. Permission test

It is necessary to check the access permissions of WeChat users in the following situations

1) Unauthorized WeChat login applet

When unauthorized, generally when using some business functions, a reminder will pop up: authorize first and then operate the corresponding function. or When submitting data to the background, it will prompt to supplement relevant identity information to submit successfully

2) Authorized WeChat login applet

Authorizing WeChat to access the Mini Program means that your WeChat account can be obtained by the Mini Program manager, and automatically exercise business operation authority as WeChat, such as consultation, payment, data query, etc.

3) The same WeChat account is logged in and authorized to view data permissions on different mobile phones

After the same WeChat account is authorized to log in to the same applet on different WeChat terminals on different mobile phones, the data and operation permissions that can be viewed should be synchronized and consistent

2. Function test

1) Test by function module

Divide according to the designed functional modules of each major category, and then refine them step by step to cover as comprehensive a test point as possible for each function

2) Test by business process

Small program business, such as consultation, payment, playback, query, and download. Connect each function point in series to form a complete business process to check; the same business may have different paths to realize, and each path needs to be covered and checked

3) Test according to data flow

According to the flow of data from one end to the input and output operation, design a test case based on the data flow. The output data may also become the input of the other end. Check whether the input data is correctly output according to the code logic, and whether the data is abnormal (cannot be input) ;input but no output;incorrect output;redundant output other information)

4) Check the validity of different entrances for the same function

In the mini program, there may be an entrance of the same function on the home page, list page, detail page, and other pages related to business functions. For example, in the paid consultation and free consultation services, you can directly enter the paid consultation entrance from the homepage, or you can use the Switch to the free consultation entrance and then switch to the paid consultation entrance. Each entry path requires a coverage check

5) Interactivity check

Generally speaking, the situations that generate data and functional interaction mainly fall into these categories: foreground<->foreground, background<ー>background, foreground<->background. The data submitted by the front desk from the A1 page may need to be viewed on the front desk A2 page, and the records will also be found on the corresponding background page B; the data modified or added on the background B1 page corresponds to the interactive change of the front desk A page, and the background There may also be an output value of the same data between different pages of itself

3. Version configuration test

Sometimes a small program makes several sets of different templates at one time, modify the configuration parameters in the front-end program code, save and recompile, you can switch from one version to another, and also need to switch accordingly in the management background , to ensure that the front end makes data calls. For the non-public part: direct switching between different versions, it is necessary to ensure that the functional modules and data independence of each other are not affected by interference, that is, the data added by the management background of different versions should only be called to the foreground applet of the corresponding template. The data submitted by different versions of applets from the foreground will only be submitted to their respective management backgrounds, and there should be no overlap. For the common part: switching between different templates will display the same content

4. Compatibility test

1) Mobile operating system

The conventional mobile phone OS is: Android (7.x/6.x/4.x/2.x…), IOS (11.x/10.x/9.x…)

2) WeChat version

For small programs that have been launched, there may be conflicts with the component support of some small programs after the WeChat version is upgraded. The situation needs to modify some components in the package of the applet synchronously and update again

5. Usability test

1) Navigation

Locate the location of a certain module on the page, return to the top or bottom, expand the navigation bar, and whether the text of the navigation label is easy to understand

2) Function entry

Whether the function entrance of important and commonly used business is in a more conspicuous position, and whether the business operation process is convenient for most users to use and view

3) Upper and lower level entry & return

Home < ー > list page, list page <-> detail page, home page <-> detail page. Whether there are corresponding buttons for easy operation of the entry and return between different levels

4) Fonts, pictures, and dynamic interaction effects

Font: label, title, content, dynamic play font. …pictures: carousel images, background images, cover images, interactive images generated by touch screen

3. Matters needing attention

1. Online

1) Online configuration

Intranet test and online test correspond to different url interfaces. Before going online, you need to modify the intranet test interface address to the interface used in the formal environment; at the same time, you must also pay attention to the conversion settings of the configuration parameters

2) Review

Submit the program package to the WeChat official for review, and the review can usually be done within 0.5d-1d on working days

3) publish

After passing the official WeChat review, you can publish the mini-program to access and use in the official environment, and you can search for the name of the corresponding mini-program through the WeChat terminal of your mobile phone

2. Common functions

1) Cache cleaning

Wechat web developer tools, mobile wechat cache clearing.

Usage scenario: check the modification effect after data modification, check the effect after the program modifies the code, etc., you can clear the cache and then check

2) compile

Used when updating beta versions. Small programs need to go through several rounds of cyclical testing and repairs. Developers will add new packages to testers after each bug fix. Testers need to delete the old version of the project program through the WeChat Web Developer Tool and re-add it. the new version of the package, then compile the debug 

Guess you like

Origin blog.csdn.net/2301_78843735/article/details/132454294