The difference between C/s and b/s test

In our daily function testing, we often divide four levels of test, unit test, integration test, System test and acceptance test according to the different test object and test target, but often overlook the application system architecture. The focus of the test is also different for different system architectures during the testing process. Following the B/s structure and the C/s structure of the special application system for example, analysis of the difference in functional testing.

The web system we talked about refers to the Brower/server access mode, including the client browser, Web application server, database server software system. The general B/s structure, are multi-layer structure, there are interface layer, business logic layer, data layer. Because this structure does not require client-side installation, the client is primarily accessed through the browser, so client-side testing focuses on tests such as client operating systems (different types and versions), client browsers (different types and versions), and client configuration (cookie settings and resolution settings). In addition to client-side testing, depending on the common technology of the web system, you need to focus on the following tests:

(1) Link test

(2) Form test

(3) Script test

(4) ActiveX Control test

c/S (CLIENT/SERVER) structure, known as the client and server structure. It is a software system architecture, it can make full use of the advantages of hardware environment at both ends, the task is reasonably allocated to the client side and server side to achieve, reduce the system communication overhead. This structure and b/s most significant difference is the need to install the client, through the client program to access the application system, so the C/S client testing is the focus, and the B/s structure is different.

The main points of C/S client testing are:

(1) Client Installation test

Ø Evaluation of installation manuals

Ø the degree of automation of the installation

Ø installation options and settings have to be tested

Ø interrupt test for installation process

Ø Installation Sequence Test

Ø Multi-Environment installation test

Ø Installation Correctness Test

Ø Repair Installation Test

Ø Uninstall Installation Test

(2) Client Upgrade test

Ø Test related to change

Ø changes to the content of the test

Ø Test related to change

(3) Client and server link test

(4) server-side data validation

(5) Client maintainability Testing

The above content summarizes the B/S and C/s system test different points, only the practice makes the theory of the tree evergreen, we can accumulate in the actual work to sum up more different test focus points.