Shulou(Shulou.com)06/03 Report--

Hello, everyone. I'm National Day holiday.

At the beginning of this chapter, we officially enter the testing work. So today let's take a look at the work cycle of test engineers. Come with me.

Remember this picture? In the chapter of "Software Lifecycle Strings", we describe this picture in detail. If you haven't seen or forgotten, please go back and have a look. I won't repeat it here.

So where is the test? Did you find out? There is a "quality inspector check (test)" in the process, which is a test, in fact, there is another test, that is, "get the clothes and start trying on them and see if there is any quality problem (test)". This is also a test. All are to test the products to see if they are up to standard.

Picture from: Baidu

Some people may ask that the heart is a customer, why did she take the test again? In fact, the role of testing is to "imitate" customers, customers buy things, so we need to meet customer requirements, then customers will certainly check whether they are satisfied after receiving the goods, so in order to improve customer satisfaction, we need to deliver customers before there is such a role to play the customer, to check in advance whether the customer will be satisfied, so there is the position of software testing.

To sum up, the test engineer is to test the software and report problems from the point of view of customer use and requirements. The problem reported is the so-called bug (as to why the question is called bug, I will mark it at the end of the article)

Before we talk about the testing process, let's clarify a few concepts:

01

The goals of software test engineers are:

Identify software defects as early as possible and make sure they are fixed. In addition, information is collected and archived throughout the software life cycle (see the test purpose below).

02

Purpose of the test:

Identify software defects as early as possible, check whether the system meets the requirements, and collect useful information for the project / group (such as what developers' coding habits need to be improved and whether the current work model is in line with the project / team).

03

Test object:

Program / project / product

Document

data

Next, let's talk in detail about the work flow of testing (in fact, it is all introduced in the big picture of the software life cycle. I hope you can really understand this and turn it into your own thing. Come on). As shown in the following figure, is the work cycle of the test (the gray part on the right is the output after each work is completed).

For the picture above, we-- make an explanation:

Requirements Analysis:

Description: the requirements are detailed, which are described in the previous articles, so I won't repeat them here. In the end, it is necessary to organize and file it into a "specification of requirements" or "specification of requirements".

Test strategy:

Description: refers to the ways and means of testing (e.g. functional testing / performance testing / stability testing) and testing requirements (e.g. testing all functional points in compliance with the requirements statement and Mission statement)

Output: "Test Strategy", now many companies put the test strategy in the test plan to write. It is usually written by word.

Test plan:

Description: the test team leader will begin to write a "test plan" according to the "requirements statement" and "mission statement". The test plan includes personnel, software and hardware resources, test points, integration sequence, schedule and risk identification.

Output: test Plan. The test plan can be in xsl format (written in excel) or doc format (written in word), either of which is usually presented as a table in the document.

Test scenario:

Description: generally designed by senior test engineers who are familiar with the requirements, the test scheme is required to design a scheme including a brief introduction of the requirement points, test ideas and detailed test methods according to each requirement point in the requirements specification. After the completion of the "test plan", an intra-group review is required. If the review is passed, the test case design / writing will continue. If it is not passed, it will be rewritten, and then reviewed again until it is approved.

Output: "Test scenario". It is usually written by word.

Test case design:

Description: mainly focuses on the design of test cases and procedures. The test cases are written according to the "test scheme" and the "requirements specification". Through the "test scheme" stage, the testers have a detailed understanding of the requirements of the whole system. At this point, we begin to write use cases to ensure that the use cases are executable and cover the requirements. Test cases need to include test items, use case levels, preset conditions, procedures, and expected results. The operation steps and expected results need to be written in detail and clear. The test case should cover the test plan, and the test solution should cover the test requirement points, so as to ensure that the customer requirements are not omitted. Similarly, test cases need to be reviewed within the group.

Output: test case set. Generally done on tools (Testlink, excel, etc.)

Test execution:

Description: execute test cases and submit quality Bug and test daily in time. Update the test case status in a timely manner. If the annotation passes, if it fails, the annotation fails and a bug is created on the defect management tool, and the reason is explained.

Output: the annotation on the test case. Callout passed, failed, suspended.

Regression test:

Description: the bug development revision will be returned to the test, which requires regression testing of bug and bug related modules. Close the bug after passing, or return to allow the developer to revise it until the test passes.

Output: status annotation of the defect. The dimension is turned off and suspended.

Test report:

Description: it means to document the testing process and results, analyze the problems and defects found, provide the basis for correcting the existing quality problems of the software, and lay the foundation for software acceptance and delivery. The final test completion requires that all test cases are passed, suspended, and all bug are closed and suspended.

Output: test report. It is usually written by word.

The label of National Day holiday:

The concept of bug: the so-called "(Bug)" refers to the hidden errors or defects in the program

The origin of bug: one afternoon on September 9, 1945, Lieutenant GraceHopper was leading his team to build a computer called the Mark II.

Suddenly, the Mark II crashed. The technician tried many ways and finally located the error of the No. 70 relay. Huo Bo observed the faulty relay and found a moth lying in the middle, which had been killed by the relay. She carefully clipped the moth out with tweezers, taped it into the event log book with transparent tape, and marked "the first example of finding a bug."

Since then, computer errors have been jokingly called bugs (bug), and jobs looking for errors have been called (debug)

-from Baidu encyclopedia

Bug suspend: it is up to the product manager to decide whether to suspend or not to resolve costly defects that are not supported by the existing technical architecture and can be resolved later. It is also up to the product manager to decide when to solve the problem.

All right, this is the end of today's content, welcome to leave a message to communicate with me! I'll see you next time.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.