Three years of testing experience turns out to be nothing, just a stroke on your resume. I always thought that with more experience, I could find a satisfactory job no matter where I was, but the reality was a big slap in the face! The kind that won't give you candy afterwards...
Let me talk about my personal situation first. I graduated with a bachelor's degree in computer science. I know python, can write scripts, selenium, and performance. However, I haven't received an offer since leaving my job until today! I have been unemployed. I started preparing my resume from the first day I left my job and started posting it. At first, I only applied for some positions that had been officially listed for a long time. I did not receive an interview invitation. All I got was unmatched feedback. I once doubted whether it was a resume-writing job. It was not good. Later, I sent out resumes in large quantities, and indeed received more than a dozen interview invitations, but I ran into a wall every time. I doubted myself again and again. Can I really not find a job when I am older?
30 is a very embarrassing age, and most companies are hesitant about programmers over 30 years old. If you hit a wall in the interview and feel frustrated, it will be even more sad if you are interviewing for a company that you really want to go to. The inner panic may be caused by repeated setbacks, starting to fall into self-doubt, not sure where to go in the future, and feeling very confused!
The latest Byte interview
Byte side:
- What is the process of testing work? What are the defect statuses? How many methods are there to design test cases?
- Let’s talk about how to design use cases for boundary values?
- Tell me what is black box testing and how to test it?
- What are the classic BUGs found in the project?
- Contents of the test plan:
- What does the test report contain?
- Test conclusion test start and end conditions?
- If a BUG is discovered, it has nothing to do with the development itself. It involves concepts, requirements, and how to solve it.
- During the very urgent testing process, a blocking problem is encountered and the corresponding development does not have time to solve it. How do you promote problem solving? 10. How do you classify the BUG levels in functional testing?
- When executing someone else's use case, what should you do if you find an error in the use case?
Byte two sides
- The difference between black box testing and white box testing.
- Have you ever done a smoke test? What is a smoke test (theoretical)?
- How long have you been working on your project? How many use cases have you written in total? How many people are involved in the project?
- Do you also test the backend management of P2P? Where is the information for personal Zhima Credit points retrieved?
- If you want to test the deletion of users in the background, that is, there is a delete button after the user name, what test cases can be written? 6. If JD.com has a shopping page for you, how do you test it? What are the main functions to test?
- Regarding the test point of adding a shopping cart, tell me how you want to test "add a shopping cart"
- How many rounds do you usually do for P2P functional testing?
- Database search for two tables
- Are you familiar with databases? Do you usually use databases a lot?
- What command is used to view files in Linux and what command is used to view processes
- What commands are commonly used to view logs and what content are mainly checked?
- How to find the error string of a.log log file
- Linux commands you are familiar with
- Is the test environment you use for testing accurate? How to set up a test environment in Linux?
Byte three sides
- Packet capture tool usage:
- Let’s talk about the difference between B/S and C/S architecture
- You are given a module test. How can you complete it efficiently in only one week?
- If you are given an app testing project that has no requirements, how should you test it?
- The language used for automated testing in our company is Java. If you don’t know Java, what should you do?
- Do you do everything when you do regression testing?
- What tools are used for requirements and case management?
- How to test a water bottle?
- How to test a landing page
- How to test a registration page
- How to test a chat box that can only input Chinese characters, with a limit of 100.
- Functional use case, test the input box of qq-app, the upper limit of characters is 100, how to test.
- How do you evaluate your cases?
- Oracle commonly used add, delete, check and modify instructions
- What is a view?
HR interview
- What should you do if you work very hard but still fail to complete the tasks assigned by your superiors? 2. What is your career plan?
- What do you do on weekends when you are not working?
- What did you learn from your last company?
- Why did you leave your job with the same salary as your previous employer?
- Where do you live?
- How much will your salary be when you leave your job?
- There are several offers
I felt like I answered well in the first few interviews, but when it came to the HR interview, it felt like it was particularly targeted at me and kept asking me questions. I also felt particularly depressed, and the ending was predictably disappointing....
Thoughts after more than ten interviews
1.Introduce yourself
Don't repeat the information in your resume. Simply introduce your company experience from near to far, and then introduce the project, highlight the technical points used in the project, your responsibilities, and your performance, and guide the interviewer to ask questions that you are proficient in. skills.
2. Don’t dig a hole for yourself
Don't bring up some skills that you are not familiar with during the interview. The interviewer will question you after hearing it.
3. Reduce the embarrassment of silence
After understanding the question, think quickly and answer in a different way if you can't think of it, or answer with an answer similar to a skill point.
Otherwise, you will never think about it and remain silent for a long time, which will not only create an awkward atmosphere, but also increase your tension, making it even harder to use your brain later.
4. Analyze the thoughts expressed in the interviewer’s words
Frequent “Uh-huh, okay.” – Identification Security
There is a brief silence, without comment on your answer. – No chance
5. The importance of automated testing
No matter what level of test engineer you are interviewing, the interviewer will ask, " Can you program? Do you have any relevant experience in automated testing ?"
You can imagine the pressure faced by those students who have been in the industry for several years but are still doing functional testing. After all, the software testing industry still belongs to technical positions. Since it is a technical position, technology must speak for itself. Continuously master new skills. As someone who has experienced it, I would like to give some advice to all testers: As a tester, you really shouldn’t just do a little bit. With the changes in the system, for current testers, it is not about automation or code. How important it is, but understanding automation, understanding code, and being able to understand system implementation have become essential skills.
So how to learn automated testing?
Since automated testing is the only way to improve manual testing, although automated testing is not that high-end, it is still essential. So as an ideal tester, how should you learn automated testing?
(1) Position yourself accurately and clarify your goals
Many students have realized the importance of automated testing, so they go to the Internet to search for information, or enroll in training classes. However, in the end, the more they learn, the more confused they become. They are stuck between knowing and not knowing, and they don't know how to go forward? What is the reason for this?
This is because you have not thought about several questions before learning automated testing: What is my real level? How much energy am I willing to invest in learning a new technology or language? If you start studying now, what should you achieve in three months or six months? Do I understand the current automated testing types or systems in the industry? If you think about these issues carefully before starting to study or train, you will get twice the result with half the effort.
(2) Comprehensively understand and choose the entry point
At present, the directions of automated testing are roughly as follows:
- Auxiliary test script direction: mainly using Shell and Python to simplify repetitive work, filter logs, etc.;
- Interface automation testing direction: Python+Unittest+HtmlTestRuner+Jenkins and Java+Httpclient+TestNG+Jenkins. Of course, there are many other secondary development frameworks or tools, but the core is the same;
- The direction of page automation mainly includes Python+Webdrver+HtmlTestRunner+Jenkins, Java+Webdriver+TestNG+Jenkins, and other frameworks and tools;
- App automation testing direction: Robotium+Java+TestNG+Jenkins,
- Appium+Java+TestNG+Jenkins, Appium+Python+HtmlTestRunner are the main ones.
Of course, what is introduced here are simple and the most basic implementation solutions, which are more suitable for introductory learning. There are various other secondary development frameworks and solutions containing many functions for you to improve in the future. Start by understanding these aspects and choose a language system. It is recommended to start with interface automation and then learn about the page and app.
(3) Take it step by step and don’t be greedy for too much.
When we improve ourselves, we find that there are many things to learn, so we become very anxious and want to learn many things at the same time. In fact, this is not good. Learning too much can easily lead to confusion and is difficult to digest. If you investigate carefully, you will find that many things are common. Code architecture, use case management, execution strategies, and continuous integration ideas can all be drawn from one example. The key is to actually implement it yourself. Write use cases based on the company's current framework. No matter how many you write, it is useless if you don't understand the overall structure.
(4) Abandon tools and use open source more
There seems to be no shortage of automated testing tools in the industry, such as QTP, RealobotFramework, LoadRunner, etc. There are countless well-known and unknown ones. Let’s not talk about the effectiveness of these tools. At present, large companies never use these tools. Everyone uses open source frameworks and tools to customize their own testing solutions.
So when you are just learning automated testing, don't rely on tools. Use open source Webdriver, Appium, Robotium, etc. to build your own automated testing project. Master the working principles of an overall automation project and prepare for building your own automation projects, tools, and platforms in the future.
Whether you love or hate automated testing, it is a necessary stage for transitioning from manual testing to test development. Maybe you have learned that automated testing is useless, has high maintenance costs, and low execution efficiency. In fact, this is not a problem with automated testing.
As someone who has experienced this, I have a deep understanding of the difficulties in the learning process.
If you are also developing in the direction of automated test development, at the appropriate age, choose the appropriate position and give full play to your advantages!
As an automated software testing engineer, how should you work hard to quickly become an excellent test development boss? This is not only a software testing engineer who has just entered the workplace, but also an engineer who has become confused after working for three to five years. Problems to face and figure out.
1.Basic questions on software testing (250 questions)
2.Linux (55 questions)
3.MySQL (80 questions)
4.Web test (10 questions)
5. Interface test (36 questions)
6.APP test (12 questions)
7.Python (100 questions)
8.Selenium (40 questions)
9.LordRunner related (80 questions)
10. Computer Network (26 questions)
11. Human Resources (55 questions)
How to obtain documents:
This document should be the most comprehensive and complete preparation warehouse for friends who want to engage in [software testing]. This warehouse has also accompanied me through the most difficult journey. I hope it can also help you! All of the above can be shared, click on the small card below to join the group and get it for free.