Software test
I used to test the software test, because I was very ignorant, just an ordinary Chinese programmer, which is also the most programmer's mentality, most "Programming is the last word."
Nowadays, it is very popular with software testing, including software testing tools, methods, theory, and technology. Because of testing, you will deeply understand the importance and interest of software testing. At this point, I have jumped out of the "small programmer" circle, and the software test is reviewed in software system engineering and project management, UML, and ERP's greater perspective.
Why do you want software testing? What is the future of software test? Who is more important for software testing tools and ideas? What is the highest realm of software testing? I have been confused by these questions. Some problems are still just have a shallow understanding, and more than the test items, the more test books, the more I feel, the more it is, more shallow . Because I am more and more infinitely infinitely infinitely, it is wide as the sea, which is deep like the universe.
Today's software testing is the same job throughout the mind, quite boring, but it is very easy to do. But it is actually. It is not easy to become an excellent software tester. Because he needs you to have strong professional knowledge and high psychological quality and communication skills in all aspects. Specifically, from the perspective of project management, excellent test engineers should have the following capabilities:
1. Communication Ability A ideal tester must communicate with all people involved in testing, with technology (developers) and non-technical personnel (customer, management personnel) communication skills. It is necessary to talk to the user, and can talk to the developer, unfortunately, these two categories have no common language. The focus of the user's conversation must be placed in the system to handle what and cannot be handled. When talking to the developer, the reorganization must be expressed in another way, and the members of the test team must be able to communicate equivalent to users and developers. Do not complicate the problem. 2. Technical capabilities generally say that developers have a despite attitude towards those who do not understand technology. Once a member of the test team made a wrong concluding, then their credibility will be immediately promoted. A tester must understand both the concept of the test software system and use the tools in the project. For example, object-oriented development language tools, database management tools, project management tools, etc. 3, self-confidence and patience developers accusing the tester to have a common thing, the tester must have enough self-confidence in his own point of view, to have a high psychological quality, allow others to refer to yourself, But don't let the programmer convince you with "this situation can't happen", instead, you should convince him, tell him that in our customers, not this. And holding the spirit of breaking the casserole, for the BUG that only has once, must find out the reason, do not solve the vow, do not give up, I believe I can repeat the bug and can overcome all the problems you encounter. 4, diplomatic power When you tell someone who has been wrong, you must use some diplomatic methods. Caracian experience and diplomatic techniques help maintain cooperative relationships with developers, and testers also need a certain diplomatic wrist when telling developers. If the method taken is too tough, for the tester, it is equivalent to "winning the war" in the future cooperation in the development department. 5. Humorous feelings will be very helpful in a humorous criticism. It is the key to the development group to be the key to test work. Try to find a "bug killer", or say "I can't believe it," I can't believe it, I didn't find bug now " . 6, a strong memory, an ideal tester should have the ability to mine similar errors that have been previously encountered from memory, and this ability is impossible to measure the value in the test. Because many new problems are different from the problems we have found. 7, the doubizic spirit is not absolutely correct, there is always a wrong place, the tester should have rebellious psychology, and others think that it is impossible, but I think it may happen. Others think it is right, but I think not right. Under normal circumstances, developers will do their best to explain all errors in the past. The test must listen to everyone's instructions, but he must keep suspect until multiple verification. 8. Self-supervising test work is easy to make you lazy. Only those who have self-supervision ability, keep a good mood, do not bring unhappy emotions in their work to work in work, so that they can work properly, otherwise they may not work. 9. Insight, a good test engineer has the viewpoint of "testing to destroy", capturing the ability of user views, strong quality pursuit, pay attention to details. The high-risk zone of the application is determined to make limited testing for key links. 10, analytical capabilities
Consider the problem to be comprehensive, combined with the needs of customers, the business process, and the system's architecture, and many aspects, and analyze the fundamental place. Flexible, smart, multi-analysis, manufacturing some examples of easily producing bugs.
11, careful
Be careful when doing testing, not all bugs can be easily identified, must be careful to find these bugs.
12. Pursuit of perfection usually programmers only consider implementing the function, but ignore how to make the program, function more perfect, run speed. The tester should point out the defects that should be bold even if the overall position of the vision is blocked. Excellent test engineers should also master the test skills in addition to the above capabilities. Although software tests have worked hard, they will make you feel more than half a skill after you have a certain skill.
1. Boundary test, test the maximum number and minimum number of values in the user input box, and when empty or empty.
2, illegal tests, such as entering letters in places where numbers are input.
3, tracking tests, tracking a process of data, ensuring the correctness of the data.
4, data testing should ensure the correctness of the data when the test is started, and then all bugs are found from the system.
5, interface testing, procedures are often easier to occur in the interface, and do not fall lightly in this module.
6, code reuse test, some module features in the development process are almost the same, and the programmer may forget the error on the original code on the original code when reused code.
7, an emergency test, an unexpected situation may occur on the server.
8, the external environment test, some systems depend on another system during development, when another system is wrong, the impact of this system is affected.
9. Repair test, where the programmer just repairs the bug, then find it, often the programmer only repairs the reported defects without considering other functions in the modification, it may cause other errors.
10, repeat test, record carefully test record After doing a day test record, the next day, according to the first day's test record, you will find an unfiffiable error.
11, text test, if there is nothing wrong in the system, I think this should be.
12. System compatibility testing, such as some programs running normally in IE6, and cannot run in IE5. Some programs can run in Win2000 and to Win98 can't run. Like some special users to use the system, you are likely to find bugs.
13. Users' ease of use of users often changes in the user, and one of the variations of changes are not convenient to operate.
Some problems considered in project management should be reflected in software testing. The content reflected is some focus on software testing. Specifically, software testing is transactional, and project management is strategic, some strategic things. Must be implemented on some transactional transactions. The software test has a lot of transactional operations, which require a good attitude to treat. Multi-summary, more designers are needed, and for problems: "If there is a change, it is not crowning."
Are you very interested in testing? However, I have to tell you, there is acid and bitterness during the test, and the taste is only you know; the test process is more like playing moving music, which makes people feel the joys, and make people feel happy, do not believe you. Try also try.
