The long-term testing has also given me a deeper understanding of software testing. Now let me share some questions that testers need to pay attention to:
Software testers should stay safe and prepared
Whenever the economy is bad and the company's performance is not good, the company may lay off employees. The first to cut is the tester. Because the tester's technical level is relatively low, it is easy to be replaced and easier to recruit. Companies often start with testers.
As testers, although most of our usual work is relatively easy. But never boil the frog in warm water. It should be self-improving, like the developers, keep learning and improve their programming level. In this way, even if you are laid off, you can quickly find a new job.
Testers should be more familiar with business requirements than developers
. The level of testers is mainly reflected in the design of test cases. To design comprehensive and wide-ranging test cases requires testers to be very familiar with the business needs of the projects they test, even more familiar than developers.
If it is a test banking system, communications industry, or ERP software. This business knowledge is very useful, and it is more passionate to learn.
How easy it is to be proficient in business needs.
-
To thoroughly read the functional requirements document, go to the PM to confirm any questions.
-
Treat yourself as an end user and often use the software you test. Simulate user behavior.
-
Memorize every function of the software.
If you are unlucky and encounter some useless and cumbersome software, you really do n’t want to learn its business (a business that you ca n’t use anymore if you leave this company)
Learn how to get along with developers
Testers must work closely with developers, so it is very important to have a good relationship with developers.
- Become friends with developers.
Familiar with everything is convenient
- Don't disturb developers
When you see developers writing code attentively, do n’t disturb others. Writing code requires concentration, if you are disturbed, it will interrupt thinking.
- Focus on asking questions.
Sum up all the questions that need to be asked, and focus on asking for development, which can save a lot of time.
- Write bugs, not to be annoyed by developers.
If the developer sees a bug description that is unclear and cannot reproduce it, he will definitely scold the tester. Therefore, the tester must write a bug, describe it accurately, concisely, without ambiguity, detailed and concise steps to reproduce, and add screenshots.
Testers should understand some basic programming.
Your product is developed in C #, then testers should have an introductory knowledge of C #. You test the web program, you must at least understand HTML, CSS, Javascript, Jquery, otherwise you test the web program for a year or two, do not know how to do this thing, tragedy.
Only if you understand the code can you communicate with the developers and not be despised by the developers.
It
is the best learning material for the testers to build the code of the development environment product. We ca n’t always follow the development butt for testing. We ca n’t always wait for the development to build a version. We will test this version and develop what code is checked in. The testers did not know at all. Occasionally we should understand how the product code is designed and how developers fix bugs. Maybe the programming level is high, and I can help the developers to do code reviews.
Use the source code tool to check out the product code to the machine. Always look at the code, often look at the code that was submitted when the bug was fixed.
Writing documents is the core competence of testers.
I remember my previous test lead saying that the reason why she can lead is because she is very good at writing documents and sending emails. Writing documents requires the ability to summarize and summarize, as well as clear logic. She is very good at analyzing dozens of pages of Spec and writing dozens of pages of test plans. She is also very good at collecting test reports. Every day, a complete, clear and beautiful test report is sent to each group, so that everyone in the company can clearly see the work of the test group.
Under her leadership, we have summarized many documents, such as "New hire checklist", "on boarding traning", documentation used by the test tool, and so on.
After writing more blogs, I found that my ability to write documents has improved a lot.
Two days of cross-testing should be done at the end of the test.
Cross-testing refers to two test engineers who exchange test items with each other. This has many advantages.
-
It is helpful to find bugs. Test engineers have measured their own projects for a long time, which is easy to form blindness. I will turn a blind eye to some bugs.
-
It is conducive to knowledge and business sharing, to avoid staff leaving and leave, resulting in unmanned testing.
-
Different test ideas, you can find many problems with each other
The bottleneck of
testers Manual test work for two or three years can basically master most of the knowledge required for testing. If you do n’t climb to the position of test lead, many people will feel the development bottleneck and repeat the test every day. Something will soon lose passion for testing.
Unable to learn things and low technical level is the biggest problem in testing this industry.
How to break through the bottleneck? I do not know either.
Automate
as much as possible. Take time to automate your testing as much as possible, which can save testing time, improve your technical level, and avoid repeated testing.
Automated testing vs manual testing
Nowadays, many companies require more and more testing. Many good companies recruit senior QA, which requires more than 5 years of work experience, masters a programming language, and has rich experience in automated testing. Of course, automated testing will be much better than manual testing.
Automation is a trend. People who only do manual testing will definitely lose their competitiveness in the future.
The technology of automated testing is far from the technology used in development.
Many colleagues wanted to switch from testing to development. Now, after a few years, they still have n’t. They originally wanted to use the accumulation of automated testing technology to transfer to development. How do you know that the technology used in automated testing is far from the technology used in development?
Test to development? difficult
Study hard to code, and then use it for testing, which is the right way
. The most frustrating part of testing is the inability to understand developers discussing technology
Sometimes meetings are held with developers, and the developers all have heated discussions. As a tester, I basically can't understand what this group of developers are saying, and I can't get in the way. I haven't even said a word in many meetings.
Excellent testers are very rare. It
is not easy to do the test well. Excellent testers need a wide range of knowledge and good communication skills (not only to deal with developers and project managers, but also to communicate with people in other groups) . Extensive testing experience, great enthusiasm and patience for testing. It also requires the testers to have extensive business knowledge and to write code.
People who write good code will definitely not do testing, but do development.
Most of the test managers have development backgrounds.
I found that several of my bosses were transferred from development to testing. They all have several years of development experience, and then do not know what is the reason to switch to test manager. They can develop and test, and they can provide technical support to their testers.
If a test manager does n’t know anything about technology, people who ca n’t hold on to the inside, and people from other groups outside the world do n’t want you.
Software testing is indeed very boring, and it takes a lot of energy. It is
undeniable that the test work requires a lot of energy, so Europe and the United States will outsource a large number of test positions to China, repeat the test again and again, and continue to execute the test cases. , Hair dizzy.
I still remember that I previously tested the upgrade of various versions of a program in Windows update. Install the old version of the program first, then restart Windows update to see if there is an upgrade, and finally uninstall it. Then install and uninstall again. The last test almost vomited blood.
English is the life-saving straw for testers
. There must be some advantages in English.
Under the same technical level, a tester with good English can enter a foreign company, which is much higher than a tester with bad English.
Minimize UI automation testing, use unit testing, and interface testing
. Automated testing that finds bugs is useful, otherwise it ’s a gimmick
UI automated testing is relatively unstable, and analysis of test results is also difficult. And the UI changes are also big. Therefore, you should try to do some low-level automated testing as much as possible. For example , the UI and logic are separated in ASP.NET MVC. The automated testing for logic is better done.
