How software testing is done, what kind of software it is, what tools or software are needed to do i

There are still requirements for academic qualifications: at least college degree or above.

Nature of work: Generally engaged in software testing in software companies, now it is generally black box testing, as long as you understand the basic functions of the equipment under test, working principles, and relevant protocol standards, you can complete the test, of course, the more experienced, your test cases will be more comprehensive, and the test results will be more valuable;

Training schools: It is recommended to find some test-related books for self-study, those training schools are honest, the tuition fees are too high, and what you really learn is just to enter the door, and you really have to rely on yourself to slowly accumulate experience after work;

All in all, everything depends on personal efforts, no matter how good the school, if the students don't work hard, they can't learn anything, the same, if you make up your mind to engage in this industry, start from bit by bit, you will definitely have a harvest...

The commonly used software testing tool is: qtploadrunnerqc

The following tools are also needed for software testing:

Functional testing tools: QTP (HP), Winrunner (MI), Robort (IBM), Qarun (Compuware).

Performance testing tools: LoadRunner (HP), WAS (MS), Robort (IBM) [must ** the corresponding plug-in to support performance testing], qaload (compuware).

Test Management Tools: Quarlity Center [the two tools are one horizontal and one vertical, and the functions are exactly the same], Rational TestManager

Bug tracking tools: Bugzilla, Mantis

Others: rational purify, rational

General Test Procedure:

Requirement analysis stage: as long as it is the learning of the business, analyze the demand points.

Test plan stage: The test team leader will start to write the test plan based on the SOW, which includes personnel, software and hardware resources, test points, integration sequence, schedule, and risk identification.

Test design stage: The test plan is generally designed by a senior test engineer who is familiar with the requirements, and the test plan requires a three-part plan including a brief introduction to the demand point, a test state and a detailed test method according to each requirement point on the SRS. The test plan also needs to be reviewed after it has been prepared.

Test protocol phase: Mainly for the design of test cases and procedures. The test cases are written according to the Test Protocol, through which the tester has a detailed understanding of the overall system requirements.

At this point, you can start writing the use case to ensure that the use case is executable and the requirements are covered. The test case needs to include the test item, the use case level, the preset conditions, the procedure and the expected result. The operation steps and expected results need to be written in detail and clearly.

The test case should cover the test solution, and the test plan should cover the test requirement point, so as to ensure that the customer requirements are not missed. Similarly, test cases need to be reviewed.

The commonly used software testing tools are generally as follows: qtploadrunnerqc software testing tools are as follows:

Functional testing tools: QTP (HP) Slow Sakura, Winrunner (MI), Robort (IBM), Qarun (Compuware).

Performance testing tools: Loadrunner (HP), WAS (MS), Robort (IBM) [must ** the corresponding plug-in to support the performance test of Dan Cluster Maintenance], qaload (compuware).

Test Management Tools: Quarlity Center [the two tools are one horizontal and one vertical, and the functions are exactly the same], Rational TestManager

Bug tracking tools: Bugzilla, Mantis, other delays: RationalPurify, Rational