The difference between app testing and web testing

1. In terms of functional testing, there is no difference between a process and a functional test. system tests and some details may be different.

Then we need to first understand the difference between the Web and the app.

Web projects, generally b/s architecture, browser-based, and the app is C/s, must have a client. Then there will be a difference when the system tests the test.

First of all, from the system architecture, the Web test updates the server side as soon as the client synchronizes. And the client can guarantee that each user's client is exactly the same. But the app side is not guaranteed to be exactly the same unless the user updates the client. If the server is modified under the app, it means that the core version used by the client user is required to perform regression testing again.

2. Performance, Web pages may only focus on response time, while the app also needs to care about traffic, power, CPU, GPU, memory.

3. Compatibility, the Web is browser-based, so more inclined to browser and computer hardware, computer system of the direction of compatibility, but generally the main browser. and browser compatibility is generally to choose a different browser kernel for testing (IE, Chrome, Firefox). App testing must depend on the phone or the pad, not only the resolution, screen size, but also the device system. The system is generally divided into Android and iOS, but the domestic Android customization system too many, it is more prone to problems.

4. Compared to the Web test, the app is more specific test:

Some unusual scenarios and weak network tests are considered. Here is the abnormal scene is interrupted, call, SMS, shutdown, restart and so on.

Weak net testing is a test that must be performed in an app test. Contains weak nets and network switching tests. You need to test the user experience caused by a weak network, with a focus on whether fallback and refresh will cause two commits. It is necessary to test packet loss and delay processing mechanism. Avoid user churn. These are already mentioned in the previous weak net test, which is no longer spoken here.

Install, uninstall, update:

Web tests are browser-based, so you don't have to think about them. While the app is a client, you must test the installation, update, and uninstall. Exception scenarios are taken into account in addition to regular installation, updates, and uninstallation. Including the installation of interrupts, weak nets, after installation to remove the installation files, updated force updates and non-mandatory updates, incremental package updates, breakpoint continuation, weak network, uninstall after the deletion of the app-related files and so on. There are too many things to talk about here, and if you have questions, you can comment or leave a message for me.

Interface operation:

Now the user of the app product is the touch-screen handset that uses, so the test time also must pay attention to gesture, the level screen switch, multi-touch, event trigger area and so on test.

The difference between app testing and web testing