Software testing This thing _ software testing

Dry for three years of time, for software testing I also have their own point of view, leaving is also the summary.

First of all, what is the right person to do software testing:

The first thing to say is that for a good software tester requirements are no better than a good developer low (although I have not done development, this phrase is not yet a confidence). And in some ways it's going to be better. In other words, a good QA should also be a good development, and excellent development may not be able to do a good job of QA. QA here refers to the real sense of QA, not pure tester.

I think the qualities that a good software tester should have:

Strong logical thinking can stand: the level of logical thinking determines how high QA can go. In the process of understanding requirements and developing software testing solutions, the ability of logical thinking determines the cost and success of software testing. What should be measured, which priority is high, which priority is low, which needs to be measured invalid situation, which do not need, what regression need.

The great picture: the development often pays attention to the detail, the test besides detail also wants the bigger picture. Good QA focuses not only on the part you are responsible for, but also on the business logic of your upstream, downstream, and even the entire system. Only in this way can the project be discovered before the implementation phase of more potential defects or even design defects, to eliminate the defects in the bud. Only by doing this can we embody the value of QA.

Delve into the spirit: the spirit of research is also a good QA must have, because in a complex system, there is no way to have all aspects of documentation, will be understood. In many cases, you need to dig 1.1 of points like archaeology to analyze what you've lost in the system.

Communication skills: must, this actually does not need to do too much explanation. Large enterprises do not have the ability to communicate, you may be a good development, but will never become a good QA.

Critical thinking: Good QA must be able to look at problems from multiple perspectives and see everything.

To add, tester and QA should be different, and in many organizations there is no difference between QA and tester. But in my ideal architecture, QA should be the work done before the implementation of the project, including requirements audits, design audits, test plans, test requirements, and other related tasks. The specific use case execution and even the writing of the use case should be done by tester. I don't know if any company is doing this now.

What is the core value of a QA team? What qualities the QA team needs to have to be able to maintain its competitiveness. What kind of people the QA team needs. Is the process really that important?

It's been 4 months since I left the Test team, and I've just written one of my test articles, and I'm going to save a little time for fun and do something worthwhile.

Why need an independent quality team. I try to avoid using the word test here, because I think that if you just test this work, you do not need a separate team, you can totally attach to the development team to set up a sub department responsible for the testing of various projects.

I think that the existence of a quality team is to look at the system from a higher altitude to different and developer angles. The QA team's work should run through a project at all times. From the requirements of a project, progress estimates, architectural design, code writing, testing, all the time to the project release should be a QA participation, or even QA should have the ability to lead.

High demands on the team mean high requirements for members and what qualities a good QA needs. My first article has written this topic, has written some basic qualities, here may specifically say. I think the team needs someone, and he has a thorough understanding of the system and needs to understand every detail of the system. He does not necessarily need to have a high code skill, but he needs to have the ability to read code and analytical skills, to the reasonableness of the requirements of his own opinion, need to give a review of design and suggestions for improvement. Can say this person tries quality Architect. The team also needs one or two innovative employees, providing better ideas for all aspects of the entire company, as well as idea for the development and improvement of test tools. This team also needs some attention to detail, good at discovering bugs, they are good at creating easy to find the bug scene, I think this kind of people need talent, rely on nurture difficult. The team also needs some patience, the person who can do repetitive work, that is tester, allows the use of outsourced staff.

Finally, talk about process. Process this kind of thing, some people like it, some people don't like it, some people like it, some people hate it. But I think like a society a country needs the law, we also must have the corresponding rules in the work to be obeyed. But it must be remembered that the fundamental purpose of the process is to improve the efficiency of the work and to facilitate communication and collaboration within the team and with other teams. But don't let process become a stumbling block to productivity gains. I think the process should be trimmed so that no additional process is required as long as the team can function properly.

This article is reproduced from the 51Testing Software test network, see more: http://www.51testing.com/html/news.html