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

Recently, a friend backstage left a message asking: "where should I start preparing for the interview?" I haven't received any invitation in almost two years. " I think many software testers will encounter such problems, so I have summed up some effective ways to improve the interview invitation rate, hoping to help newcomers in the industry and test professionals who want to switch their current jobs.

First of all, you need to know about software testing!

Basic concepts of testing

The first basic thing is the concept of testing. You need to be very good at this, especially manual testing. But only know that different testing concepts only get half the job done. The next most important thing is to know which type / technology / concept testing can be applied at which stage of SDLC.

Classic definition: testing is the process of executing a program to find errors.

IEEE definition: the process of running or measuring a software system by manual or automatic means to verify that the software system meets the specified requirements and to find out the differences from the expected results.

Principles followed in software testing

1. Testing can show the existence of defects, but can not prove that the system is no longer defective.

two。 Exhaustive testing is impossible and conditions for timely termination should be set.

3. Testing should be carried out as soon as possible.

4. The defect has clustering characteristics. Defects in the system may be concentrated in the bug of a small piece of code.

5. The pesticide paradox of the test. If you test with the same test case all the time, it is easy to have different types of bug, and the system should be evaluated frequently and tested with different cases.

6. The twenty-eighth principle of testing. Considering the efficiency of testing, you should spend 80% of your time and energy testing 20% of the important modules.

7. The test activity depends on the test background. The testing of the financial and banking system focuses on security, while the testing of the communication system focuses on the stability of the system, big data.

The test engineer should use it out of the box.

A very important part of the test engineer is "out of the box". If you can't use it right out of the box, trust me, the test is not for you. What does it mean to use it out of the box? Don't just follow traditional methods and implement new things in testing, try to summarize automation and regular testing work. Think from the user's point of view. Think about how users will use your application. What common mistakes can he make, or what tasks can he perform on your application? In this way, you can learn more about any application and help you answer questions in depth.

Skills that must be mastered in testing

In addition to curiosity Learning, you should also upgrade your skills in the following areas:

1. Some practices of basic database / SQL queries and concepts.

2. A basic scripting language (for automated testing).

3. Network and system management concepts will help you control the project in the system.

4. Don't just write UI test cases, check what's going on inside the application. Applications with database connections check for data updates, retrieve and should not lose data under any circumstances.

5. Grasp the project. Understand the application in the test before you start the test. Instead of looking at requirements documents, look at architecture documents, design documents, sequence diagrams, and activity flowcharts.

How to improve the interview invitation rate?

1. Clear content module division and refined content of each module

For example, the common division: personal information (necessary)-major experience (company and school)-professional skills-project experience (detailed).

two。 Focus on work experience and project experience

Project experience focuses on your responsibilities, contributions, and highlights in the project.

This is the focus of the resume and the most important point of the interview.

Resume writing and interviews are skillful: to highlight what you are good at and what the interviewer may be interested in, bring the interviewer into the urn.

3. Prove one's ability with numbers

For example: how many use cases have been written and how many bug have been mentioned? What is the improvement of App performance and the decrease of Crash rate?

For the company to save xx costs, efficiency optimization how many times; employee evaluation (10 to 1000) accounted for the proportion and so on.

Ps: operators and product students are more sensitive to numbers and performance, while software test engineers may not be good at this. It's good to dig regularly.

4. Neat format and orderly paragraphs

Being able to write a neatly typesetting document in Word should be a basic requirement for Internet practitioners, but the proportion that can be done is really not high, just two points: neat typesetting and orderly paragraphs.

5. PDF version

The Word version may be messy on Mac, and there will be eye-catching symbols such as line breaks when opened.

By the way:

(1) the resumes derived from many recruitment websites cannot be opened on Mac.

(2) headhunters will change the contents of your resume, and you need to make sure he doesn't delete anything.

6. Clearly write down the starting years of the school and each company

7. Write nouns correctly (don't lose points on small details)

IOS is not ios,Android, not android,GitHub, not Github.

Correct writing: Java, App, MySQL, GitHub, SDK, JS, JSON, XML, etc.

In fact, there is a very simple principle of case, similar to the naming of variables in the program, the first letter between different words is capitalized, except that the general first letter needs to be capitalized (while the first letter of the variable name is lowercase).

Such as:

App is the abbreviation of Application.

SDK is the abbreviation of Software Development Kit.

IOS is the abbreviation of iPhone Operating System.

8. Keep your resume at about two or three pages.

Not too short, not too much information, too early project experience can be omitted or taken, the general interview will talk about one or two major projects on the ok.

Of course, if you are good enough, ok a blog address (the attitude seems a little arrogant, ), and try to focus on your project experience in detail, which is also a process of combing yourself.

9. Email title and simple greetings

Email and resume attachment title use name-position-phone number as far as possible.

10. Resumes are often updated and deleted.

I have received nearly ten pages of resume, more than ten years of work experience, a decline of the project, including internship experience in school.

Ps: resume content should be concise, the most important thing is the recent experience of one or two companies, a lot of unnecessary profiles or just skip, two or three pages can not be more.

Summary:

When you get an interview, you must be prepared for the interview, whether it's technical questions or career planning questions, and answer them calmly. Most importantly, be sure to understand the interview company in advance, including the company's development history and major product lines. In this way, in the interview process can be better play!

Welcome to join the 51 software testing family, where you will get [latest industry information], [free test tool installation package], [software testing technology], [job interview skills]. 51 learn and grow with you! Looking forward to your joining: QQ Group: 755431660

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.