If you do black box testing, your boss will ask you what to do on the Linux operating system

Let's learn and practice as you go.

There are many books for performance testing, just go to the bookstore and choose the one that suits you.

Software Test Engineer: Quality management in a software enterprise.

What do software test engineers learn? That's a lot, let's talk about test cases today:

Test cases have always been a difficult problem, many friends always say that they can't write or write, in fact, after experiencing learning, you will find that some test cases are not difficult at all.

Test case templates.

Zui small function test set: used to verify whether the system meets the basic functional requirements in a simple and high-speed way (Zui small function set can be fully automated);

Complex test set: used to further verify that the system can function properly with complex or uncommon legal inputs and operations;

Robustness test set: It is used to test whether the system can respond normally in various abnormal inputs, abnormal operations or abnormal environments, and to detect whether the system can operate normally after an error, whether it causes data loss, whether it destroys other related software and hardware, etc.;

Note: ZUI small test sets, complex test sets, and robust test sets are all written according to requirements and using test case design methods. The UI is written according to the product UI design document.

When writing test cases, you need to consider the following questions:

Why is it important for functional test cases to cover all requirements?

Is it effective to make it easy for others to review? Which test cases are easy to add, delete, and modify?

Test cases with a tree-like structure and clear hierarchical relationships. Auditors typically check whether the branches are fully covered and redundant, and then the leaves are comprehensive and redundant. With such a hierarchical relationship, users can also maintain test cases well.

Which test cases are easy to share across multiple projects? Why separate functionality from UI test test sets?

In test case design, separate the function from the UI test case, so that for the same functional requirements, the functional test case can be common in multiple projects. In order for functional test cases to be common across multiple projects, functional test cases need to be described in common terms. The UI use case should only describe some of the constraints of the UI of each product, refer to the following ** module test use:

When the dialpad does not enter a number, the keyboard is "grayed out", etc., this constraint is related to the specific project and belongs to the UI use case.

Requirement module division.

Before designing a test case, it is important to fully understand the requirements. On this basis, the requirements are divided into modules to form a demand tree (note: when dividing modules, the requirements can be repeated.

But the repetition should not be too much, otherwise you need to think about whether the divided modules are reasonable? ）