Conditions for software test engineers

Are you qualified as a software testing engineer?
Author/chililaduzi time/13:50:00 category/comprehensive view/62
View comments in Forum Mode
Tags:
1. Proactive
What kind of work attitude is the most important aspect of evaluating a tester. If a high-level Tester (purely technical) does not have a good working attitude, in a test team, a tester who is willing to work, even if his technical skills are not high, is not smart, but he is responsible for his work. Everything you tell him can be done seriously. This tester will also play a major role in promoting the testing work. This is also one of the main reasons why many companies are willing to allow people who have just joined the job to perform tests. In addition, whether or not the tester is active at work also affects the development of a tester. For example, one of my testers will learn qtp by themselves when they are idle at work, improve his technical skills so that he can use this test tool to perform automated testing in the next test, it not only improves work efficiency, reduces work intensity, but also creates better development opportunities for itself (because of the good effect of qtp, It is promoted to the test team lead ). Therefore, it is very important for a person to take advantage of work time and take the initiative to learn. Another example is similar. One of my testers, when their test tasks are terminated abnormally while other test group tasks are busy, I took the initiative to participate in the testing work of other groups, not to mention the technical level of him. This kind of attitude that asked him to work would allow him to show off from others, which attracted my attention, naturally, he will pay special attention to his work, and every communication will let him learn a lot of new things.
2. Be careful and not afraid of trouble
It cannot be said that testing is a cumbersome task. If you are not a serious, careful, and trouble-free person, we suggest you do not enter this industry. Otherwise, in the end, you must be yourself.
One sentence: The Details determine success or failure, which is especially suitable for testers. When testing requirements are met, each requirement point in the system requirement report written by the developers will become several testing requirements in the test requirements (you need to verify the normal situation, exception). Sometimes people feel like playing a game of permutation and combination, but there are too many situations in this game of arrangement and combination. If you are not patient enough, if you are not careful enough, it is easy to omit test requirements, and these omissions are often caused by problems (developers are also easy to forget to consider these issues to generate problems ), in addition, the input data of the test work is a very cumbersome task. For example, a date validity test can easily summarize 3 and four hundred test data, what is the number of testing tasks you want to perform. What's even more terrible is that testing is not a one-time task, and regression testing is often required. All the tedious tasks must be repeated constantly. When repeated tasks are repeated, testers are often afraid of trouble, reduce the number of test cases, resulting in incomplete testing. Therefore, being conscientious, careful, and not afraid of trouble is a required quality requirement for a good test.
3. Strong learning ability, good at summing up
When I took part in my work in, it was difficult to find a software engineering book. When I first came into contact with the test in, there were almost no books on testing, these problems have greatly hindered the improvement of my level, but they cannot be an excuse for us to improve our own level. In the past 97 years, our tests were mainly functional tests, at the beginning, it was also a gorilla test. Later, on the one hand, we searched for test materials from professional books and summarized our own experiences. After one year, we basically formed our own test procedures and methods, we have our own test plan compiling methods, test case compiling specifications, and test summary methods. New testers can quickly improve their own levels, later, we used this method to learn test tools. During the course of qtp learning, one of my subordinates learned for three months and basically mastered the use of qtp, he also summarized the problems frequently encountered when using qtp and published it on 51testing. Many people think that he is a technical expert. In fact, he only worked for 8 months, I have been a beginner for three months. Continuously studying new technologies, constantly summarizing problems encountered in actual work, solutions, and summarizing them are the best way for testers to improve their technical skills. There are two more points to note: 1. With the increasingly professional testing work, the original low-level testers are increasingly unable to meet the needs of testing, the use of testing tools, and the update of testing theory, the application of new technologies requires testers to constantly improve their own skills. 2. Good testers should not only understand the testing technology, A reasonable test plan can be developed only when you have a good understanding of the tested system, development environment, tools, and system architecture. That is to say, the test owner should not understand the testing technology, we also need to understand the mainstream development technologies, architectures, and tools (although we do not need to become experts). All of these require continuous learning and summarization by testers.
4. Master the Testing Theory
Development tools are changing, test tools are changing, tested systems are changing, and everything is on the edge. What is the most important thing for a tester to learn, I personally think it is the study of testing theory. Taking my own example, I used to do pure software, but now I have been exposed to many hardware-related tests, such as mobile phone tests, however, no matter what system you test, the basic theory remains unchanged. First, developers must provide better Requirement documents. Summary design documents, detailed design documents, and Requirement documents are the criteria for us to develop test requirements and the criteria for us to determine whether the system is faulty, detailed design documents are the basis for creating test cases. Our division equivalence classes, boundary value testing, and other basic testing methods all require the support of these documents. Of course, each test of different types has its own special features, for example, mobile phone testing requires you to have a certain understanding of the Communication Theory (that is, the system environment), so good testers must master the testing theory. If you think your testing theory is good, answer the question about performance testing, load testing, and stress testing.
5. I don't know what to talk about, but I am in front of the charge.
Some of my testers always like to pay attention to me, but never think about how to implement it. what they like is how intelligent I can be at a glance, my Adviser is good (I used to do the same ). I want to tell you that such a person has actually fallen into a misunderstanding of his or her technical career. Seeing the problem shows that you have a certain level, but how to solve the problem and how to implement it truly reflect the individual's level, at the beginning, Chinese scholars refused to practice what was terrible because they were afraid of killing their heads. This bad habit is now called a low eye. Only when solving practical problems can we find out the shortcomings in our solutions and what new problems will arise, so as to continuously improve our work. A simple example, I have been using TD for a long time, but today I can still find some new features of TD and use these features in my work to improve my test management, therefore, I personally think that good testers are always the testers who are at the forefront. In actual work, they are the best way to improve their functional capabilities.
6. Interpersonal Relationship Processing
Testing is a burst of problems. Especially for units with nonstandard development processes, how to deal with interpersonal relationships is a skill that good testers need to master, as a test leader, developers, testers, and company leaders often face a short period of testing time, continuous regression testing, abnormal termination of testing, criticism from leaders, and responsibilities of developers, testers complain about the duration and test environment. How to resolve conflicts and deal with these problems is a standard for measuring the quality of testers. In fact, a major problem is misunderstanding. Developers, the misunderstanding of the testing workload by company leaders is one of the main reasons for these conflicts. As a good tester, besides some common interpersonal skills, we also need to be a good propagandist who constantly publicize the testing methods, theories, and workload to developers and superior leaders so that they can have a correct understanding of the testing work, only in this way can we really deal with the interpersonal relationship between the testing department and other staff, which is a good direction for the unit testing.
7. Familiar with development tools and platforms
I am tired today. I will not talk much about it. I cannot perform unit tests without understanding the development platform, and I cannot perform performance tests well.