H5 and applet test point analysis

Recently, I have come into contact with more tests on H5 pages. Except for the business logic function test, the test methods of other parts of the H5 page test are basically universal. Here, some general test methods for H5 pages and small programs are summarized and shared with Everyone.

H5 advantage:

1. H5 can be cross-platform, and the development cost is relatively low;
2. H5 can be updated at any time when it goes online, which is suitable for rapid iteration;
3. H5 can reach users lightly and provide faster services;
4. In the WeChat portal or On the browser, users only need to click on the link to obtain the services we provide.

H5 disadvantages:

1. H5-> conversion strongly depends on the browser;
2. Currently, H5 basically cannot store data locally and relies on real-time data. When the network status is not good, it will freeze and cry.
3. Relatively low performance, affecting user experience.

H5 function verification

1. You can return through the return function of the H5 webpage (not the return function of the mobile phone), and there will be no situation where you cannot return.

Return logic:
1. For the return in the page, and the test of the return returned by the browser. The return in the page should consider the business logic. Returning to the corresponding level requires transition logic returned from the user's perspective, and an infinite loop cannot occur. And pay attention to whether you need to refresh the page after returning. Request to return through the return function key of the H5 page (not the mobile phone's own return key), and you can return to the correct page (upper level/exit H5). Click the return and back keys to return to the page Is it the desired page.

2. The horizontal and vertical screens can be switched between each other, which can be self-adaptive, and the layout will not be messed up; or the page only supports horizontal or vertical screen restrictions.

3. Click on the mobile phone from the list to enter the detail page, and open it in the original window, so that you can return through the back button on the page header instead of the back button on the mobile phone, which is more friendly in terms of interaction.

4. Pay attention to page requests, whether there will be redundant requests, or there will be redundant data returned after the request, try to streamline as much as possible, otherwise it will waste traffic.

5. Picture adaptation test, adapt according to different screens and resolutions, and the definition after adaptation, take double-sized pictures for high-end machines – app compatibility test.

Small program testing technology

Features of Mini Programs

1. Similar to WEB. Not HTML5
2. Ready to use, ready to go
3. Has offline capabilities
4. Based on WeChat cross-platform
5. Comparable to native operating experience

The entrance of the applet

1. Scan the code to enter the applet
2. Search for the applet
3. Send the applet to the desktop (Android)
4. Send to a friend

Small program structure

1. The framework of the WeChat applet consists of two parts, the View view layer and the App Serive logic layer. The View view layer is used to render the page structure, and the App Serive logic layer is used for logic processing, data requests, and interface calls. They are in two threads run.

2. The View view layer uses WebView to render, and the App Serive logic layer uses JSCore to run.

3. The View view layer and the App Serive logic layer communicate through the JSBrigdage of the system layer. The App Serive logic layer notifies the WebView rendering of data changes, triggers the WebView rendering page update, and the WebView rendering notifies the triggered event to the App Serive logic layer for business deal with.

Small program test point

1. Functional test

Input
Output
Boundary value
Page interaction - interface interaction in the WeChat applet
System problem test - low battery, incoming calls, plugging and unplugging of data lines, charging status, restarting, etc.

2. Interface test

Is the design beautiful
? Does it meet the requirement description
? Is the size reasonable
? For horizontal and vertical screen switching, use different mobile phone resolutions and sizes?

3. Compatibility testing

Operating system—IOS, Android
WeChat version—api (interface) library of applets
Other WeChat applets
Screen size and resolution factors
Tests under different network conditions—2G/3G/4G/WIFI

4. Interaction test with WeChat function

Entrance – drop-down box, discovery module search
Transaction – WeChat wallet, WeChat card package
Switching with other WeChat functions – grab red envelopes, text chat, voice chat, video call

5. Performance testing

Page response time
Resource usage
Rendering time
Power consumption
White screen time Frame
rate

6. Security testing

Interface testing – the security of transmitted data
Dangerous account authorization
Associated with the app account of the applet

7. Usability testing

Whether it is convenient to use
Whether the prompt information is complete
Whether each function is available Whether
it is easy to find
Whether it can be used offline
Whether the process of entering the mini program is simple and easy to operate

8. Other precautions

Mini-program upgrades and updates – generally mandatory upgrades and updates. Mini- programs
currently do not support sharing to Moments, but they can be shared to Moments in the form of pictures .

Guess you like

Origin blog.csdn.net/nhb687095/article/details/131680566