Testing experience
CsdnItsThe essence of waterProduction, please visit http://blog.csdn.net/FantasiaX
Small order:
I have been doing tests for more than a year, and occasionally I will calm down to think about some problems, but many of the results of my thoughts seem like a flash of light-I forgot it later. Unfortunately, remember it later.
Body:
Technical Thinking
- Any part of software engineering-from requirement analysis, architecture design to the final debug-can introduce bugs. Sometimes it is a single introduction, and sometimes it is a nest of introductions. Therefore, excellent testers should have a wealth of software engineering knowledge. It is hard to imagine that an engineer who does not understand material mechanics and structural mechanics can accept the building that has just been built.
- The tester not only needs to learn programming, but also needs to learn a variety of programming. Preliminary testers can observe and use software from the user's perspective in order to find out the bug, but senior programmers need to use the program principle to analyze more profound things. It is no exaggeration to say: if you want to deeply test web programs, you should learn hacker; if you want to study. net programs, you should learn msil; if you want to debug native code in depth, you should learn to compile and understand the PE file format; if you want to test the security of software, you should learn to crack; if ...... In short, the ideal tester should be at a deeper level than the programmer.
- Keep your liking and enthusiasm for software. From flashget to 3DS MAX. If you have a chance, you have to get started. In this way, you can enrich your software experience, establish your grasp of the Software Logic virtually, and enrich your industry software knowledge, for example, if you want a person who has been using Outlook for a long time to test Photoshop, the results will certainly be far from those tested by a person who has been using Photoshop for a long time.
- An in-depth understanding of the operating system, including the Windows series (including. Net platforms, but also part of the operating system), the Linux series (JDK is part of the operating system), and The maccompuch series. First, the software is actually rooted in the operating system of trees and plants (through the system open to the programmer's API and the system is connected); second, many software is cross-platform, you must have rich experience in multi-platform operations before you can play. For example, many excellent products of Adobe are cross-Windows and Mac platforms. The APIs of these two platforms are completely different, why does the software look exactly the same? For example, many products of IBM are cross-platform Windows and Linux.
Behavioral thinking
- Software testing is not omnipotent, so testers are not omnipotent. The tester is not the savior. This illustrates at least two problems: 1. A software with poor design and poor coding can no longer be used to test it. 2. testers (or Software Quality Assurance personnel) do not have the right to be arrogant in the team, and swing around with bugs to prove their good faith through the test results-everyone is equal. The concept of equality is especially lacking in Chinese thoughts.
- The tester should be a thinker. Therefore, the test team should have an independent, quiet room without a computer for in-depth and meticulous thinking.
Management thinking
- Do not pretend to understand. You don't understand it. It's not enough for the team members to look down on you. If you don't understand it, all the team members will look down on you. Management is management. It is to do a good job of the project, not to let you practice and fight, you must uniform the team members. Be brave in asking questions, asking questions, and learning quickly. This is the way for a team to learn.
- As a lead, if there is nothing important to do, leave when it comes to the point-or your team members will stay with you in the face. Have you ever thought that he might want to accompany his parents, wife, and children? If you often do this, we suggest you take a look at the fable of $20.
- To be authoritative, not to be a schoolmaster. What I want to say is: the speed and breadth of the subordinates are determined by your mind and extensiveness. Most junior managers have a narrow mind and a low degree of extensiveness, which leads to the habitual "absolute consistency" of the team ". As far as I know, the Indian program is not like this. subordinates and leaders, newbies, and authority can calmly discuss their differences without losing their ears. My suggestion is: in a team, do not have a hierarchical concept, be equal, be ironic, be respectful, be tolerant, or be humble. In a word: everyone is an ordinary person. Who can be with whom?
