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

For an enterprise, whether it can survive well, there are four core indicators, product quality Q, service quality S, product price P, response time T. In my opinion, the two core indicators that belong to the technical category are: one is product quality, and the other is response time. To improve the core competitiveness of enterprises, the goal is to improve product quality, and quality is the lifeblood of the enterprise. how to better protect product quality and protect products for front-line sales is particularly important.

As an employee, we share the same breath with the enterprise, share a common destiny, strengthen the awareness of product quality and improve product quality. So what can be done to improve product quality?

Personally, I am a software testing engineer, so what efforts should I make in my daily work in order to make a contribution to improving product quality?

First of all, we take the software testing process as the norm to analyze what testers can do to improve product quality.

1. Requirements review stage

At the beginning of the project, identify those potential defects or errors to prevent these errors or defects from being left out later in the project. Therefore, in the requirements review phase, we should do:

① makes relevant query and confirmation records before the review.

② should agree on responsibilities, goals and projects.

two。 Prepare test plan, scheduling phase

The preparation of the test plan includes the required resources, task scheduling, schedule, risk analysis and so on. We should make it clear:

① works out the test schedule and task schedule

② prepares the test environment

③ formulates the standards for pre-release and stop testing.

④ formulates testing strategies and methods.

⑤ determines test risk

⑥ determines additional information about the resources required for the test

3. In the use case review stage, we should pay attention to:

The structural arrangement of ① use case design must be reasonable and clear, so as to cover the requirements efficiently.

② needs to cover all the test sites required.

③ reasonably arranges priority testing

The ④ use case should be well executed, and the preconditions, operation steps and expected results of the use case should be correct and clear.

⑤ removes redundant test cases as much as possible

⑥ should design test cases from the user level

4. In the course of testing, how can we find more problems as soon as possible?

The stability of the test environment should be ensured in the early stage of ① testing.

② should be well prepared, the goal should be clear, and the users should be understood correctly.

③ adds version control to track and record the entire software development process to avoid confusion between code version and test version or code conflicts between development and development.

Then we discuss how to better control the product quality from the aspect of the enterprise itself:

1. The rationality of product demand design.

The rationality of product demand design is very important. It is necessary for PM to do sufficient demand research in the early stage, to get in touch with users in the front line, to have a deep understanding of users' most commonly used scenarios, to think about product logic from the point of view of users, and to solve users' pain points.

2. Technical architecture design and logical implementation (design) should be reasonable.

Avoid problems in technical framework design, and consider more about the rationality, efficiency, performance and so on of implementing logic.

3. Develop the coding specification

Specification is not a restriction on development, but is more conducive to improving development efficiency; standardized code can also reduce maintenance costs, greatly improve the readability of the team's code, and help code review

4. Requirements review

Correct and effective requirements review, check in advance, record problems, and review with questions, which is more efficient and effective.

5. The specification of testing process.

According to the actual situation of our own company, reasonable testing procedures can improve efficiency, avoid pm, rd, qa bickering back and forth, and better control product quality. At GSX, we have PC and APP testing processes, which are roughly divided into test requirements analysis, case writing, case review, interface testing, smoke testing, test4 round testing, beta testing, monkey testing, and submitting testin for compatibility testing. Online environment regression test, installation, uninstall and upgrade main process test after release

6. Specification of development process

According to the current stage of the company, if multiple R & D is developing multiple functions at the same time, the code needs branch development, and the test environment has no bug, then merge the backbone, and when submitting the code, the necessary review,sql must be online and the necessary review must be carried out to avoid the paralysis of the whole station caused by a sql.

7. Specification of the launch process

There are many branch teams in some research and development, and the maintenance of the public code base is very messy, and sometimes it is easy to cause major online accidents, so it is necessary to agree on a standard online process to ensure that the code with no problem in the branch can be merged into the trunk and then return to the backbone as a whole.

8. define the scope of optimizing functional testing.

Sometimes when rd optimizes a function, there is no problem with qa testing on one side, but it may cause problems on the other side, so selecting the test scope scientifically and accurately is also a deep knowledge.

9. Interface testing, unit testing

In general, when the backend completes the interface development, you can advance the test to the QA partner and start the interface testing on the server, which can expose the implied Bug in advance, allow developers to repair Bug at the first time, make functional testers more comfortable during testing, minimize the number of underlying Bug, and make the product development process more smooth. Then improve the efficiency and shorten the product R & D cycle.

10. UI check

Very often, when the product is on beta or online, it is found that UI is inconsistent with the design, so the inspection of UI is also very important, and it is even more necessary to step in at a critical point in time. It is best to go through it during the smoke test, and check it after the test environment test to ensure that there are no UI problems caused by later modification of bug.

11. Measurement and prevention of bug

Regular bug distribution analysis, online bug analysis, to find the real reason for the emergence of the bug, bug frequent functions, scenarios, models, etc.

12. Operation and maintenance monitoring

The operation and maintenance level should also achieve a very perfect monitoring system, including network layer, operating system layer, application layer, interface layer, port survival, process survival and page-level monitoring.

13. Necessary review and summary

Review and summarize in time at the end of each project, and make timely adjustments to the problems in the process of the project, so as to prevent the team partners from repeating the same problems next time.

14. Establishment of communication mechanism

In many cases, the bug is caused by inadequate communication, and we will encounter a lot in the actual process of doing the project, so we should try our best to maintain a smooth communication environment and way to organize daily station meetings, rapid borderless communication, information synchronization, timely communication and solution to problems, and improve efficiency; so we should pay attention to this point!

15. Human cultivation

The cultivation of people generally needs from these aspects, technical level, way of doing things, communication and cooperation ability, active communication awareness, sense of responsibility, execution, learning, effective time management, positive and optimistic, willing to help others, willing to share, and never complain, can make the positive side, infection to drive others

Product quality management master Juran once said: "quality is designed, not tested." this sentence proves that to improve product quality, in addition to corresponding tests to ensure quality, we should also start from the source, do a good job in early planning, strengthen process management, supplemented by appropriate product inspection, always follow the PDCA principles, and improve product quality is just around the corner.

Summary

Now most of the operational accidents since the launch of products are caused by product or process problems. Either because the previous release process is not perfect, or because the developer typed the version incorrectly, many of them can be avoided. Now we improve the product release process. All the products are tested on the local server first, and then switch to the external network server for users to use. Clear personal responsibilities, after the occurrence of operational accidents, according to the reasons to investigate responsibility, the development of personal performance appraisal system. To further improve the operation process and system.

In short, if you want to get high-quality products that users are satisfied with, everyone is responsible for management, demand, development and testing.

Summed up very well, in the future, when you get a product, you should consider it in an all-round way to avoid stepping on the pit. Share with you ~

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.