Letter from a project manager to the tester

Teams TestPersonnel:

First, I want to say to you: hard work! Thank you for your efforts throughout the project development process. Your credit for the project's final success! I would like to take this opportunity to explain some testing knowledge to you and hope you can apply itWorkIn practice, we will add some competitive weights for our future.

My score belowSoftware TestingSummary, testing basics and TestingConfiguration ManagementI hope it will help you in three aspects.

I. Test Overview

Software testing is not something that comes out of nothing, and with the progress of the times, its position is growing. In fact, software is written by humans, so it is not perfect. Since it is not perfect, there must be defects. In this sense, software testing is permanent. As long as the software exists, testing cannot be avoided.

Software testing is a critical task. Since its birth, testers have to be discerning and demanding. In addition, they also need some intuition and inspiration to mine defects hidden inside the software, exposed to the world. This is actually a great job.

Of course, there are rules for testing. Software testing requires a solid theoretical foundation and solid working ability. You need to read the customer requirement analysis documents, product manuals, project schedules, software design documents, and write test plans and test cases, defect report, useAutomated TestingTool, which requires clear measurement statistics and summary.

In fact, it is impossible to perform a full test of the program, and software testing is risky. Of course, testing cannot show all potential defects. These are easy to understand, but they are not necessarily desired. For example, what should I do if I want to test whether "insecticide" has enough efficacy? In addition, some principles seem easy to understand, such as those foundBugWhat does it mean? Is there fewer bugs or more? Also, not all defects need to be repaired. Can you find examples that prove this theory?

This is the test. It is not a so-called click-and-click task. It is a complicated project. It is filled with profound theories and, in a sense, it contains art. To become a good tester, You need practice, experience, long-term efforts, and persistence.

Ii. test basis

The threshold for testing is low, low, and high. It is necessary to have a certain foundation. You must be able to differentiate between static and dynamic tests.Black box testingAndWhite box testing, Distinguishes between manual and automated tests, and can even combine dynamic white box tests or static black box tests.

The above is not complicated. We can give some simple examples to prove it. For example, a static black box test is used to check the product specification, and a dynamic white box test is everywhere-isn't unit test exactly?

There are also theories such as logic-driven coverage testing, basic path testing, and computation of Sphere complexity, as well as different technologies such as JUnit in Java.Unit TestAnd so on, these will be of great benefit to your future work.

These foundations are essential for your entry into this industry. With this foundation, you will be able to take a longer and smoother journey in this industry.

Iii. Configuration Management

When you are working on a project, I am afraid you have already felt the importance of configuration management. This kind of experience does not come from the infusion of books, but from the real experience.

For example, for Bug Management, you can find a bug, write it in an Excel file, and then send it to the developer by email. After receiving the bug, the developer will make targeted changes and then send feedback via email. Open the previously submitted bug registration form again and review the feedback from developers. It is possible that the above process is still repeated. The problem is that as the project continues to deepen, the number of exposed problems will also increase. Such interactions are more frequent. Looking at the tracking history of a bug seems like a wishful thinking, but it is beyond reach.

We need to manage the configuration of this process and the entire process of software development in a better way. Improve and optimize the process through tools, so as to improve the efficiency of our work and ultimately ensure the quality of our project.

In fact, this project is not so complex. Imagine that the project is more complex, the environment is more complex, there are more developers and testers, and how to work together and communicate effectively, how to ensure that the project is completed according to the schedule will become a very huge project. For example, we have a development environment, a test environment, and a formal environment. How can we control the Code submitted by developers and ensure the similarities and differences between the three environments? This process is required, dedicated tools are required to ensure the accurate operation of these processes.

Software is carried out around people, tools, and processes. It is people-oriented, upgraded with tools, and guaranteed by processes. Software is not a simple collection of human resources, it is not a simple collection of work, the story of "man-month myth", I have told you before, and now I want to tell you again. For example, it is common sense for pregnant women to have children in October. However, if you want to pursue the progress, ask 10 pregnant women for help. What is the result? Needless to say, everyone knows. There are many risks in software development, no matter what development model you adopt. However, we will make full use of these theories, do a good job in the process, and do a good job of documentation will help us reduce risks.

Well, write it here. I hope this letter will be useful to everyone.LearningIt is helpful and I wish you all the best to go further and achieve your own ideals.

From: http://www.51testing.com/html/index.html