Application SMS

From the perspective of functional testing alone, APP

Testing, network

test

There is no difference between process and functional testing.

According to its different carriers, the differences are as follows:

system structure

Web project, b/s architecture, browser-based; As long as the web test updates the server, the client will synchronize the update.

App project, c/s structure, must have a client; app; application

If the server is modified, all core versions of the client users need to pass the regression test.

Performance aspect

Web project

Need monitoring

Response time, CPU, memory

Application project

In addition to monitoring

In addition to response time, CPU and memory, monitoring is also needed.

Flow, electricity, etc.

Compatibility aspect

Web project:

1.

Browser (Firefox, Google, IE, etc. )

2.

Operating system (Windows7, Windows 10, Linux, etc.). )

Application project:

1.

Equipment system:

IOS(ipad, iphone), Android (Samsung, Huawei, Lenovo, etc. )

、Windows（win 7、Win8）、OSX（Mac）

2.

The mobile phone device may be based on

Mobile phones of different models and resolutions

relative to

marry

Projects and apps have special tests.

1.

Interference test: interruption, incoming call, short message, shutdown, restart, etc.

2.

Weak network test (simulating 2g, 3g, 4g, wifi network status and packet loss); Network switching test (reconnection after network disconnection, 3g switching to 4g/wifi)

Wait a minute. )

3.

Install, update, uninstall

Installation: Interruption during installation, weak network and deletion of installation files after installation should be considered.

Unloading: Need to consider

Do you want to delete the application-related files after uninstalling?

Update: mandatory update, non-mandatory update, incremental package update, breakpoint continuation, and update in weak network state.

4.

Interface operation: Regarding the testing of mobile phones, we need to pay attention to gestures, horizontal and vertical screen switching, multi-touch and background switching.

5.

Security test: whether the installation package can decompile the code, whether the installation package is signed, and permission settings, such as accessing the address book, etc.

6.

Boundary test: less available storage space, no SD card/dual SD card, flight mode, system time error, third-party dependence (QQ, WeChat login), etc.

7.

Permission test: set whether the App can obtain this permission, such as whether it can access address book, photo album, camera, etc.

Testing tools.

Automation tools: applications

be in common use

Appium

net

be in common use

selenium

Performance testing tools: applications

be in common use

JMeter

net

be in common use

LR、JMeter