Interview: Testers must have skills, are you ready? _ Software Testing

Recently had the opportunity to do some interview work, mainly is responsible for interviewing the software test personnel to recruit the technical interview.

has been the role of the applicant, after a number of interviews, how many also accumulated a little experience in the interview, now has a role change. The first interview met a working life longer than me, there is no time to carefully understand each other's resume, plus the candidate more "strong." The interview situation is rather bad.

There are alumni who say, alas. No, you lost a candidate. It would be nice to have a few more faces. This is not just the loss of candidates, the interviewer's impression of the interviewer is more important. Interviewer's ability and performance for the first time interviewers often represent the company, more specific is the ability of the Test team.

If the interviewer is very "water", this water two aspects, one is not easy to interview, thinking is not clear. Second, the technical capacity of water, ask for half a day to ask not to the key points.

So as an interviewer, the impression of the company will be discounted a lot, even if the interviewer can afford the expected salary, the interviewer will have to consider what you can learn, whether the work is challenging, whether there is room for development.

Therefore, the interviewer's ability and performance is equally important to the success of the interview, after all, in the interview process is a two-way selection process. The following discusses the skills that testers should have.

In the course of this discussion, I am full of personal prejudices and preferences. Don't like to accidentally spray.

The above is a system diagram I have drawn, which is relatively generic, and of course special requirements for the tester's skill requirements.

Basic knowledge of software testing:

This piece is actually nothing to discuss, if you have six months to a year of work experience, there must be a clearer understanding of this piece, of course, in the actual work does not require you to each test method to root for the source, know the meaning of these methods and application scenarios.

Writing a variety of test documents is a bit difficult for beginners. But in the end there is no technical content of the matter, if the business and process is familiar enough, the document use case will naturally be written.

Test Assistive Skills:

I found that these two skills in the written and interview process must test, the occurrence of high probability, but in the actual work, some tests do not touch Linux, some tests do not need to operate the database. Of course, the test, also can not be too on the surface, also need to familiarize familiar with the relevant test tables, understand the system server.

Fortunately, the requirements of these two skills are not high, Linux most of the test several commonly used commands, SQL General test to increase, delete, check, change.

Automation Technology (UI):

Most alumni have a QTP automated test tool in their resume test skills, and when I get up and talk to him about automation, the big answer is that I know and learn this tool. This also can not blame testers, who let full street on the written "requirements familiar with LoadRunner, QTP and other automated testing tools." "In fact, they do not have the company." So many companies are demanding that it seems necessary to learn the tool.

For me, I don't care much about the skill of the tool. For Web applications, it's more about how much you know about front-end technology. Because the object you want to automate is the various functions that the front-end technology presents. Do not understand it, how to locate and manipulate it.

UI Automation is not just qtp a tool, if you master a language, the road to automation is broad, you must know there is also called Selenium (webdriver) automation tools, you do not necessarily know that Ruby has a watir framework can also be done automatically, Maybe you don't know that Python has a splinter framework that can also be automated. Then you don't even know that Python has a pywinauto framework that automates the Windows GUI. You don't know that there are too many tools for automation. Talking about these will have to involve programming technology. In comparison, QTP does not require much programming power.

For automated testing, another concern is your understanding of automation and what is appropriate for automation. How your automated test cases are written. What use cases are suitable for turning into automation. How you are going to implement it. What are the strategies for automating the work. You need to automate what you expect and effect in your project. Just learn the tools and take an example to practice. It is difficult to have a real understanding of these problems.

Performance test:

Loadruner seems to be more famous than QTP, doing tests must play tools. Not touch LR are embarrassed to say that they are doing testing. Performance testing must be accomplished by means of tools. How to simulate hundreds of concurrent concurrency without using tools.

The biggest difficulty, other is to the system architecture understanding, in fact, more time does not need to reach the architect level, even does not have to reach the development level, but at least, you need to understand what operating system, what database, what development language and framework, what middleware. You need to know how to monitor these things. You know, call development and play.

For performance testing, another test process that I am more concerned with, what is the purpose of your performance test. New system validation. Or the expansion of the old system. What is expected to be achieved. Can be carried out in an independent environment. Where the pressure is, why the script is recording this way. Do you really know the meaning of your test results? Or to the system can make a reasonable assessment, or to provide guidance for systems tuning, or to the system to make a basis for expansion. If the cause and consequences are not clear why to do it.

Programming Ability:

Programming is not limited to language, most students will also have the necessary skills to write a resume, familiar with C language or some other language. Mostly stops at university C language level. There is no chance to use it in the work. Therefore, there is no chance to further enhance the capacity of this area. It seems quite reasonable to say that you are testing and not developing.

However, I personally paranoid about this point, as for the above automation, performance will not matter, if the ability to understand a little bit of programming one or two, I will vigorously recommend. Understand programming and do not know how to program the depth of the system is not the same, a little understand can only see this is the button, that is the input box. Know how to program your login is a <from>, the input box is a <input>, your login submission is using the post or get it. The logic layer is to obtain the input username password is to check the database to compare. In the test process, regardless of the implementation of the function or bug, will be more thorough, so it is easier to dig out related bugs.

Generally understand the programming I will let it write a small program, such as the number of primes, recursive call, with an asterisk (*) print a trapezoid, if the test work to write a number of scripts such as auxiliary testing is a big bright spot. Don't think it's "difficult" for you to write a program. Usually pay attention to accumulate this how difficult.

What are you looking for in the new job?

"I want to have access to some performance tests, automated tests, and so on, because the previous work has been doing functions." ”

Most testers think that the process of upgrading themselves is this:

Now there is a performance requirement, then lead to find you say, Xiao Zhang Ah, you study the performance test bar. We now need an urgent need for the system to do a performance test, and then, you go back to start research performance test, spend one months finally understand, start to the system performance testing. Finally finished the task.

But the actual situation is this:

Now there is a performance requirement, then lead to find you say, Xiao Zhang Ah, you will do performance test. A, this has not done before, you have to study. The leader said: Oh, that's it. Xiao Wang you go back to understand it. Because Xiao Wang has not done, but he usually do the test for a longer time, for the new technology more love to delve into. In the opinion of the leader, Xiao Wang can fix the problem in a shorter time. If this demand is urgent or require more professional, the leader will directly recruit a professional to do performance.

So, the conclusion is very clear, the opportunity is for the prepared person. If you keep accumulating on a skill, there is always a time to shine.

The interviewer more time is looking for the bright spot, I only have one post, in the interview 10 people, 10 people all can put the test process what to say Shunliu (although I also only recruit one to understand the test will flow on the line). Eight people say they know QTP, LR and other tools, only two people really have the experience of automation or performance testing, only one person programming is not bad. Who do you think the interviewer will choose?

The bright spot is also the conversation (talking about the capital of money), you and the previous interviewer is similar, the former interviewer wants 5K, you want 8K, then I prefer the former, if you have other people do not have the bright spot, then I am more inclined to have the bright spot, I would like to recruit a cow B, salary is not I give you open, finally whether to talk about is you and personnel or superiors of things.

The interview is a comprehensive process, if you are clear thinking and agile. If you have the same habit of blogging as I am. Or talk about the two technical books you've read recently. Let me see you are a very enthusiastic person, you are a love of technology. This is not the same as other people's bright spot. Sparkling. Shines everywhere.

End. More Popular articles: http://www.51testing.com