Applet testing
- Preparatory
(1) micro-channel version number for an in 6.3.27 and above, is inferior to the upgrade.
(2) qa required to apply the experience of those rights correspond applet & developer permission.
(3) applet development version, trial version, the official version.
(4) applet AppID , the project addresses & names.
(5) clear Applets This entrance test & version.
(6) micro-channel public platform release number of [small] program development assistant, can be convenient preview and experience the online version, the version and the development version of the experience.
- Test Points
(1) Authorization : Authorization has been achieved silent, that is, a user first visits a small program, the initiative to obtain micro-channel authorization by acquiring openid , generating around uid , and storage nickname, picture and other information. When subsequent users to re-enter the applet to kill without re-authorization.
(2) Function : the inner end of the normal test function is tantamount;
(3) Cache : After functional requirements, then you need to focus on the situation cache:
① micro letter provided to each applet 10MB local cache.
② for caching brought account switched, release, at present, the solution is simple and crude applet will be deleted, re-enter into force.
③ page switching when possible on the next page of data will be taken to a page to show, for example, [the main program - a red envelope demand] Click " unused " to display the correct copy - "click " used " or " expired "- "click " unused " , copy it to show " used " and " non-use " of the copy. At this point you can give developers mention bug , page caching to solve the problem through code;
④ solve the problem from the code level cache:
1) Clear the current stored in the storage in the content, such as cookie information, call the main wx.clearStorageSync () ;
2) 2 from the base library 1.9.90 Start, small supports automatic updating on-line codes, the interface is wx.getUpdateManager () .
(4) Performance
(5) Share function test :
① Share to friends list & generate posters page to a circle of friends to share;
② with online / test / share with friends, landing page development version ( intro ) is the corresponding line / test / development version;
③ circle of friends jump is identified on the web; during the test if it relates to a jump scan code, it requires the use of [] applet code testing tool.
(6) Service notice : The template ID push service notification form;
(7) micro-channel public number :
① to be concerned about the public number & no need to collect formId ;
② applet notification service: collecting formId ;
③ formId validity 7D , if the user is not available formId , you can not push the corresponding message to the user;
④ by clicking on the operation of a single / bulk collection formId , mainly stored in WTable , trigger behavior such as payment, submit the form etc; Detail stabbed at it https://mp.weixin.qq.com/debug/wxadoc/dev/api/notice .html
⑤ bulk collection formId : the POST request, such as zzwxpush / addFormIds
⑥ single collection formId : GET request, such as zzwxpush / addFormId formId?
⑦
⑧
⑨ Each applet collected formId , only for the corresponding applet only for the corresponding UID . E.g. idle Co. 108 batch collection formId , but stored in the applet 103 , resulting in idle Co. batch formId failure, and many small stores invalid program available formId , mainly due to the front end of the incoming parameter source = 103 leads.
⑩ problem often occurs: formId invalid (hit applet own strategies), no available formId (to be collected).
(8) hierarchy :
① M page, Toast , pop, etc. are not limited to the level of the problem;
② applet native about page 10 after layer can not open a new page, normal or closed loop business processes easily lead to 10 level issues, such as personal center - "product list page - " personal center ......
③ solution strategy [level]: The memory pages link to Storage , then refresh the page links to pull stored return. Currently only path to save the page, the page does not save data.
(9) Compatibility:
① micro-channel version: Interface applet is completely dependent on the micro-letters, some of the higher base library interfaces may not take effect in the micro-channel version of the low, the need to make compatible, such as: sharing within the page is based on the 1.2.0 base library development, thus requiring the corresponding micro-channel version 6.5.8 and above;
② different models: as a page in Huawei models show no problem, but to show millet models but there is a problem;
③ phone systems: Android and ios two versions compatibility may vary; personal home page [Andrews and ios ] evaluation style in question.
(10) Buried:
① buried inner end point test and the test is substantially the same procedure, attention actiontype & pagetype parameters;
② small statistical procedures often require the user to distinguish between sources, and therefore need to focus [ backup ] in the Channel , pagechannel , of the type and other parameters.
AppID ③ : primarily stores applet source parameters.
SCENE ④ : scene value, details https://mp.weixin.qq.com/debug/wxadoc/dev/framework/app-service/scene.html
Channel ⑤ : only for small page program entry into force, will accompany the entire life cycle, until you exit the applet. If there is no clear parameters, the default is none .
Pagechannel ⑥ : for the page url parameters, only to the landing page, not to the subsequent pages. If there is no clear parameters, the default is none .
Of the type ⑦ : currently used in the details page, distinguish this product is mainly used for personal mine / circle group / others Normal .
⑧ according pm demand may also increase the corresponding channel parameters.
(11) Embedded M Page:
① 1.6.4 version began to support applets embedded in M page.
② M page is not limited to the page level applet, such as Games M page] Click Home - "Game Channel is a layer of the page, rather than the 2 layers page.
③ Test M Page adapted accordingly required to enable normal use of small programs, such as landing and the like. If the M page embedded native page, you also need to do additional native adapter page interaction. Games such as - my mission to fight] do not fit, you are prompted this error.
④ M test page jump to focus on function, exhibition and other issues.
(12) test pits :
Applet often encountered during the test pit, the focus needs attention:
① level page jump
② Compatibility
③ Cache
For details, please check out the links https://testerhome.com/topics/16299