Software testing Experience

Copyright Notice: Welcome to reprint the comment, hope to indicate the source reproduced, easy to have a problem to discuss. https://blog.csdn.net/jsd2honey/article/details/90975460

Project summary

－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－

Testing Stages

1. The company's own projects using iterative development, a large version of the annual, quarterly small version, each version must be repeated regression testing, functional testing for the first time, the purpose of testing the current version features no problem, upgrade the second test, the purpose confirmed the new version of the data is compatible with older versions to upgrade from functioning properly, the third functional test, when the objectives of the upgrade function properly.
2. Each version should have special testing phase, such as interface testing, performance testing, security testing.

Test document output

1. After the project needs assessment, or project has been launched to discuss needs, you should communicate with the project manager and start thinking about what testing.
2. Involved in the test environment, we need to build a good test before, if set up high technology, research and development should be completed and exchanges to work together and build a detailed document recording, and precautions.
3. Test document is not missing, such as test plans, test plan, test cases, test reports. The purpose is not just to write a document the company accumulated wealth, more of a sort of test their ideas and reflection.
4. Each stage of the test should have output, such as the planning stage, the output of the test plan, test plan, test case execution phase output, after the system test output test reports. The entire testing process should be tracked, there are documents you can be tracked.

Testing focus

1. Testers need to have the bigger picture, to grasp the overall project requirements and individual responsible for liaison between the test part of the demand.
2. Demand needs to think how dimensions, such as general demand made by the user, including the explicit needs and the needs of the invisible, more explicit demand is reflected in whether to implement the function of user needs, the needs of some users expressed stealth is not in place, such as security requirements functional module, performance requirements, easy operation requirements, easy to expand demand.

Communication Skills

1. To do more homework before the needs assessment, and more to express their demands, perception of the product;
2. When a review embodiment, must be clear, use cases requirements correspond, with both multi-dimensional embodiment;
3. The development and testing process to confirm a problem and needs to actively communicate, to help develop the positioning problems, and promote problem solving;
4. When communication and development, as far as possible in terms of the impact on the user extent of the problem, it is more persuasive.

Attention to detail

1. Writing test matrix to increase the amount of color-coded, and better comparative analysis.
2. Some more complex testing tasks, make clear the test environment (machine model, CPU type, cable type, memory size, operating system version, patch level, and other parameters), shot during testing of critical data evidence.

Testing tool record

1. Web functional testing, test rule out the need for cross-browser compatibility issues with multiple platforms (Windows / Linux) in a variety of browsers (Chrome / IE / Firefix).
2. Automated testing tools robotframework, gitlab, hudson & jenkins.
3. Packet capture tool wireshark, burpsuit, f12, fiddler.
4. Security tools, sqlmap, burpsuit, nessus, appscan.
5. Performance testing tools, LR, jmeter, zabbix,
6. Test environment to build tools, openstack, vmware, vsphere, docker
7. Real-time log reading tool, tailf, EKL (ElasticSearch / Logstash / Kibana)

The establishment of software testing knowledge

1. With a project test team, unified software testing knowledge is worth promoting, for example, to achieve the level of software testing division.

The establishment of software development knowledge

1. In-depth testing requirements need to know more software development and architecture knowledge, system architects can refer to knowledge

The direction of development planning

－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－

Test management positions

1. The relative technical prefer to communicate with the outside world yearning
2. Good communication skills, strong organizational skills of people.
3. Long-term compressive ability, the leadership can withstand criticism, can withstand lower subordinates complain. Grievances can stand and eat at a disadvantage.
4. For full management of persistent passion.

Performance Test Specialist

1. Relatively more hi human accidents digital expression
2. Computer hardware limit on interest, like pressing the hardware as much as possible potential.
3. The various components of the well known principle of computer, communications and computing-depth study of the limit.

Automation Test Specialist

1. Develop proficiency in a language.
2. Familiar with the business.
3. Familiar with a variety of test scenarios.

Security testing experts

1. Willing to learn and study, concerned about the latest security vulnerabilities.
2. Familiar with the industry and products.
3. Proficient in a variety of testing tools.