Software testing and Learning (1)

I. the early development of the software industry is similar to looking for a virgin land. For example, if no antivirus software exists, you can create one. There is no translation software. You can make one, but when the market is gradually saturated and there are several other types of software competing at the same time, the competition is the quality of software and the market demand of software. The quality of software is just what needs to be improved through software testing;

Ii. the software on the market is written in many different languages, for example. net, written in JAVA, so the total demand for Software Testing engineers should be. net java total number of developers in all languages. It is enough to explain the huge demand of testers;

Iii. The number of low-level testers is relatively large because the entry door is very low. Senior and middle-level testers need to have a solid foundation of computer knowledge and even development capabilities. Therefore, there is a large gap in personnel;

Iv. The specific circumstances of each company vary. If a general testing process is adopted, the efficiency and loss are the greatest. Therefore, we usually find a suitable method and then select a suitable solution and test tool for testing;

V. the most ideal and standard test process:

1. After obtaining the detailed requirement analysis from the customer, the developer can start to write the unit test script to verify the correctness of the Code that has not been written before the developer actually writes the code;

2. Then, compile the software that passes the unit test every day to perform the smoke test;

3. Perform the integration test, which may be done by testers or by developers, similar to the gray-box test;

4. The integration test mainly tests interfaces and core modules with high usage;

5. Choose a variety of suitable testing tools based on specific requirements for integration testing;

6. After the integration test is completed, the system test will be conducted. The requirement specification is required for system testing, but it is a pity that the general requirement specification of domestic enterprises is basically not good. So in this case, the more feasible way is to look at the software itself;

Vi. IBM's Rational testing philosophy:

1. knowledge domain: contains functional testing, performance testing, and runtime analysis (in fact, it cannot be called a test, because the running results are not correct or wrong, but only some running information inside the program, refer to later development );

2. Process: Assign relevant personnel the skills in the relevant knowledge area for testing;

Vii. For testing, after obtaining the project, the company will deploy the entire test process, select various solutions, and finally implement each of them;

Viii. The test tools have a wide range of options, such as Mercury. They all have a complete set of tools used in each phase of the test;

Ix. IBM's latest Rational development philosophy is: to put the idea of integration and integration into development tools. If programmers need two different software for software development and testing, the efficiency and ease of use will certainly not be placed in one software. Therefore, many test plug-ins will be used in development tools;

X. The future of software testing can be developed into highly automated testing. No need to write basic code or basic testing is required. Of course, I am still alive;

Xi. Currently, the testing tool is mainly composed of recording playback and script-driven tools. Therefore, it mainly solves the workload of testers rather than automated testing;

Xii. Has such a test philosophy: because developers generally perform some tests during development, developers can write test scripts, which is more efficient. However, it may be difficult to develop a project, because some parts may remain unchanged after delivery;

Xiii. The image of developers is as follows: developers are targeted and have clear goals. 2. the testers are fish fishing and the scope is more important than the target;

Xiv. The skills of senior testers are mainly experience, so tools cannot be replaced;