Recruitment of software testing Engineers (I)

Over the past two years, in the face of overwhelming software testing, the promotion of the Golden profession and various software training, I have the feeling that software testing is coming in the spring. But actually? Looking at what I know about the company, it is not so optimistic (if it is a frog at the bottom, please correct it ). It makes me feel that blue-collar software testing is not long. We should think about and explore how to keep ourselves as competitive as possible.

First of all, let's talk about every aspect of a software testing engineer. It can also be said that it is a summary of professional requirements.

Basic common sense

1. Basic computer knowledge

2. Basic computer network knowledge

3. Basic knowledge of software testing (software quality, basic knowledge of software quality management, software testing concepts, software testing standards, software testing technologies and methods, and software testing project management)

4. Basic software development knowledge (software engineering knowledge, understanding of software development methods and processes)

Technology

1. Programming Language

C/C ++, VB, Vc, Java,. net, ASP, JavaScript, etc. The specific requirements depend on the company's specific projects or products. However, C is generally the basic requirement.

2. database knowledge

SQL Server, Oracle, MySQL, Sybase, etc. Generally, testers must use SQL statements to query, modify, add, and delete data.

3. Operating System

Windows, Linux (commonly used RedHat, Suse, Debian)/Unix (FreeBSD, Solaris, HP-UX, Aix, Mac) systems.

Automated testing tools

1. Automated Testing concept/automated testing framework

Many people think that automated testing is the use of automated testing tools. In fact, various tools are only an effective tool for Automated Testing implementation. How to build an automated testing framework out of tools is far more complex than studying how to use the testing tools, there are many difficulties.

2. Automated Testing Process

3. Use of automated testing tools

L automated testing framework (process)

L automated functional testing of GUI

L automated functional testing of non-Gui

L Performance Testing (Performance Testing in the broad and narrow sense)

L automated testing tools (functional testing tools, performance testing tools, defect management tools, and test management tools)

2 (HP) Mercury Interactive quicktest pro, winrunner, LoadRunner, Quality Center (test ctor), and sitescope

2. compuware qacenter (testpartner qarun qaload qadirector trackrecord), devpartner Studio

2 (IBM) Rational testsuite (robot testmanager functionaltester extends merancetester ClearQuest clearcase ...)

2 (Borland) segue silktest silkperformer sctestmanager

2 others: JUnit, nunit, auto it, test effecect, opensta, etc.

Practical (work experience)

1. Testing Process of the company

2. The company's specific defect management process (submit a bug report and track the bug status)

3. build and manage the test environment

4. Preparation of test plans, test cases, test reports, and other relevant documents

Language

1. English

2. Japanese

3 ....

Character

After 30 minutes to 1 hour of interviews, I tried to find out if the interviewer's personality was suitable for software testing.

1. Be careful and pay attention to details

2. Be patient and not afraid of trouble

3. Good communication skills

4. Excellent learning ability and strong logical thinking

5. Proactive

6. Strong ambition, never meeting the status quo