Go: Parse software test content from the Web three-tier architecture

b/S architecture system, will use the following basic software architecture:

Data access layer: To achieve access to data functions, such as adding, deleting, modifying, querying data.

Business Logic layer: realize the specific logic function of the business, such as student's entrance, drop-out, achievement management, etc.

Page display layer: Display the business functions on the browser, such as pagination display student information.

In a real-world project, you might add tiers to the business logic layer depending on the situation, and the 3-tier architecture will be involved in testing or testing the 3-tier architecture for software testing .

Data Access Layer:

1. The frequently occurring problem may be that the database field length is incorrect, causing the saved data to be truncated or to prompt for errors.

2. The data written is correct.

3. There is also often a developer database operation that fails to function when the table name and field name are written incorrectly.

4. Part of the functionality to complete the change when it is necessary to ensure that everything is fine, this involves the correctness of the transaction.

5. Exception processing of the database layer.

6. Unreasonable database design leads to performance problems, such as unreasonable database integrity design, garbage accumulation resulting in performance degradation, index design and so on.

Business Logic Layer:

1. Gaps in demand development are not tight enough to lead to the development of code with business requirements errors. A previous experience is a boss who does not know the software originally in the development of the requirements, no data deletion function, but later need to increase the deletion of data function, but not after the requirements of review, after the development of the completion of the test, after the basic data deleted, the module referencing the data will not work properly;

2. The business logic and the process and the demand do not conform, boils down to the developer's understanding to the demand is not thorough;

3. Some other requirements do not meet the requirements, such as safety, information standards, performance, etc.

4. Coding error. Mainly includes local data structure error (variable initialization, address overflow, etc.), boundary condition error, module interface error, code independent path error, improper handling of exception, etc., which involves the detailed unit test and integration test;

5. The errors caused by the software design architecture, such as the caching mechanism, need to be considered in terms of performance and timeliness, otherwise the submitted data cannot be seen in time.

Page display layer:

1. Front-end JS error, such as length or format check error, etc.;

2. Localization errors, such as errors caused by the user's use of different habits, multilingual translation errors, etc.;

3. Page display, such as content display is not complete, display error, interface color mismatch;

4. Usability is not good, such as page navigation error, prompt language is not friendly, not easy to learn, etc.

5. Compatibility errors, such as resolution compatibility, browser compatibility, keyboard and OS compatibility issues.

In the usual test work, but also often encountered other problems, such as configuration of the error, including the configuration of the Web server, the configuration of the site config, and so on. These affect the usability of the software.