How do you do software testing? What is software testing?

Software testing is the use of this testing strategy and method to verify whether the performance of the program meets the needs of users. The test process is divided into 1

Analyze the requirements 2Write test case 3Execute Test (Use Case) 4

Fill out Report 5Submissions are divided into phases:1

Unit Test 2Integration Test 3Confirmation Test 4

System Test 5Performance test 6Installation Test 7

Acceptance testing For software testing, we must first have a suitable testing process, and we must master the basic testing strategies and testing methods, especially for functional testing, which is mainly to use this testing method comprehensively, such as boundary values, equivalent classes, etc. Secondly, you need to have a wide range of knowledge, such as the development language needs to know, Linux

UNIX and good analytical presentation skills in documentation and verbal communication. and mastery of such testing tools, as well as scripts for automated testing, etc. If you need it, you can come to me, I hope it can help you.

Of course, QC, TD, BugFree, etc., in terms of test management, automated testing, LoadRunner performance.

QTP function. This needs to be different depending on the needs of different companies. So try to master as much as possible, and you can go to that company. It's basically all figured out. If necessary, you can talk to me q, 137277583, answer: ginger.

Our company is like this: testers write test cases according to the requirements document--- test the functions that are done first--- regression if the test fails--- pass the test--- and finally test the whole system.

If necessary, test the downforce, safety, performance, etc.

Software Testing TheorySoftware TestingSoftware Testing Definition? A series of activities carried out in order to find errors. Details:

According to the specifications of each stage of software development and the internal structure of the program, a batch of test cases are carefully designed, and these test cases are used to execute the program to find program errors.

What is the purpose of software testing? With the least amount of time and software testing theory Software Testing, Software Testing Definition? A series of activities carried out in order to find errors.

Detailed: The process of carefully designing a batch of test cases according to the specifications of each stage of software development and the internal structure of the program, and using these test cases to execute the program to find program errors.

What is the purpose of software testing? Find out all kinds of potential bugs in the software with minimal time and manpower. As many problems as possible are found and corrected before the product is handed over to the user, to ensure that the product is finally handed over to the user.

The primary responsibility of testers is to "find bugs" in our ordinary people's eyes, and they need to use various testing techniques and tools to test and find defects in the software, so that developers can better optimize the product and make it safer and smoother for users. Specific points include:

1. Formulate test plans, test data and test cases according to software design requirements.

2. Set up the test environment and execute the test cases.

3. Submit the test report.

4. Track bug modifications, and constantly test and improve products.

5. Test other aspects of the product.

Of course, this is not the final work, because software testing runs through the entire software life cycle, so it is also necessary to check the online and upper functions, feedback on the current version and improvement suggestions, etc., so that it can be regarded as a relatively complete final end.

What is the career path of software testing?

For technical personnel, career development planning is generally divided into two directions: technology and management.

Newcomers who have just entered the software testing industry will start with the most basic execution, followed by use case design, which is equivalent to basic functional testing. Subsequently, everyone will be further refined according to their personal career development, and some will take the management route and become supervisors, managers, project leaders, etc.; Some in-depth test case design and continue advanced functional testing; Some of them develop technology, specializing in performance testing, security testing, automated testing, test architecture design, etc.

If you want to deepen your career in the technical field, it can generally be divided into two categories: one is functional testing, which is the point test and black box test that everyone is relatively familiar with. The other type is automated testing, including functional automation, performance automation, interface automation, etc., this kind of work has relatively high requirements for the best ability, that is, the test development engineer is often called.

The main work content of software testing includes two aspects: verification and validation.

Verification is a series of activities that ensure that the software is performing some specific function correctly, that is, to ensure that the software is doing the event in a pure and accurate manner.

1.The process of determining whether a product at a given stage in the software life cycle meets the requirements established in the previous phase.

2.Proof of the correct and dull form of the procedure, that is, the process of using formal theory to prove that the procedure complies with the provisions of the design specification.

3.Conduct various activities such as reviewing, reviewing, testing, inspecting, auditing, etc., or judge and report on whether certain processes, services, or documents are consistent with the specified requirements.

Validation is a series of activities and processes designed to verify the logical correctness of software in a given external environment. That is, to ensure that the software does what you expect it to do.

1.Static confirmation, not actually executing the program on the computer, proving the correctness of the software through manual or program analysis.

2.Dynamic confirmation, by executing the program for analysis, testing the dynamic behavior of the program to confirm whether there is a problem with the software.

The object of software testing is not only program testing, software testing should include the documents generated at all stages of the entire software development period, such as requirements specifications, outline design documents, detailed design documents, and of course, the main object of software testing is the source program.

The process of software testing is as follows:

1. Demand analysis and demand review

The first step is to do a demand analysis, based on the requirements specification and prototype drawings of the project received by the assessment center.

1) Read the requirements specification first, be familiar with the basic requirements of the project, and have a general framework idea for the project;

2) If you have enough time, you can use the method of drawing a flow chart to clarify your needs and your own ideas;

3) Look at the prototype diagram carefully according to the requirements specification, have a thought about the destination of each field, and consider the jump between pages;

4) In the process of the above steps, sort out the problems that need to be focused on and cannot be understood, and use discussions with colleagues or confirmation with the project manager to solve the problems and destroy the training.

2. Write a test plan

Writing a test plan is generally about who does what at what time, and what is produced in the end. That is, which modules the tester has to test, and which documents to submit, and in what period.

3. Write test cases and review use cases

The test case is the document that guides the test, for example, we want to test the functions such as logging in and buying things, and design the test case through the test method and strategy.

Review is evaluation review, and you can't take it for granted how to measure. You can't just enter the correct username and password, just log in and you're done. As a soft test engineer, you need to be destructive, such as what to do when the password is entered incorrectly, whether there will be corresponding errors, and so on.

4. Test development

In the first round of functional testing, first of all, we should pay attention to the fact that the mainstream process can be passed, there are no problems that hinder the process, and if such problems occur, communicate with the developers in time to solve the problems;

In the second round of functional testing, we focused on the individual functions of each disturbance balance port, which can be fully realized without obstacles, and all function points can be realized;

In the first round of system testing, each port is integrated together, and the interaction of each port can be realized normally, and the interface and user experience are concerned.

Compatibility testing, including APP and web pages, is afraid that the compatibility test adapts to mainstream devices according to the equipment test of the evaluation center; The webpage needs to be compatible with mainstream browsers such as Google, Firefox, IE, 360, etc.

The specific steps are as follows:

1. Refine the testing requirements according to the needs of the project and product.

2. According to the test requirements and the overall plan of the project, formulate the test plan and test plan, including the time node arrangement of the test, the arrangement of human resources, the test strategy, etc., and review it.

3. According to the test requirements and related design documents, write test cases, that is, clarify the specific operation steps and expected results of each test point, and review the use cases.

4. Prepare the test environment and test data, including the hardware environment and software environment for the deployment of the test system.

5. Execute test cases, submit bugs found during the testing process, and conduct regression tests through version iteration Kai Nai to verify relevant bugs.

6. Complete the functional test of the internal software system, after the system test, the system tends to be stable, and submit it to the customer for acceptance test.

7. Write software test reports.

8. Summarize the test process and archive all documents in the test process.