How to summarize your software testing work

What does software testing do:

1. Demand review

The first thing the team does after they get the requirements is to do a requirements analysis to see what the requirements are to be implemented by the software. The next step of requirements analysis is the requirements review, which requires the participation of software test engineers and product requirements personnel, developers, and QA personnel to review whether these requirements can be realized.

2. Write a test plan

Next, while the developer writes the development plan, the tester writes the test plan, which is who will do what test work at what time, and what work results will be produced, that is, which documents will be submitted.

3. Write test cases

A test case is a document that guides the testing work, such as the login function and purchase function of the system, and the test case is designed through the test method and strategy. Therefore, writing test cases is the most important job for software test engineers outside of testing.

Fourth, use case review

A use case review is all about evaluating and reviewing whether the test method and test content are reasonable and comprehensive. It is not only necessary to do basic testing work, but also to comprehensively conduct tests that may cause a variety of errors to minimize bugs as much as possible.

5. Perform tests and submit bugs

Needless to say, the test engineer actually does the test work, finds the bug and submits it for the software developer to modify.

6. Regression testing and writing of test summary reports

Regression testing is to re-test the software that the developer has fixed bugs to see if the bugs have been modified. After the bugs are modified, the tester should write a test summary report to explain the quality of the software before the software can be released online.

Pay attention to bugs, how to find, how to solve, etc. are all things to be done in the test, and there is a summary of these details in the source code era, and the content is still very detailed.

Software testingThe scope of work includes:

1. Modify the test case;

2. Test with automatic testing tools to find software defects as soon as possible and ensure that they can be closed;

3. Project feasibility, reliability analysis, and risk analysis.

4. Formulate a test plan;

5. Test automation development.

Responsibilities: 1. Provide services for senior management: that is, the test department will report the test report of the product.

It is provided to the top management, and the relevant decisions are made by the top management. The test report should include what the top management wants to know about the product: error discovery rate, error correction rate, problem convergence trend, etc.

2. Provide services to the project manager: The test report provided to the project manager should meet the needs of the project manager, including: what are the unmet functions of the product, what are the problems in performance, what problems have been communicated with the programmer, but no agreement has been reached, and it needs to be submitted to high-level arbitration, etc.

3. Provide services for QA: testers participate in quality management.

The activity should be of a service nature, i.e. he does not lead the quality management activities, but provides service support for the quality management activities. Through the test report, the tester uses facts and data to reflect the quality of the product and provide a basis for the work of QA.

4. Provide services for programmers: testers should make friends with programmers, give timely feedback to programmers on specific program problems, and work with programmers. On the one hand, the tester usually knows the business domain better than the programmer, so he can test the functionality of the product from the perspective of the salesman. On the other hand, the tester passes the test case.

It can find problems that programmers don't think of easily.

The main job content of a software tester is to conduct software testing according to the test plan and test plan; Able to develop test models, develop test plans, arrange test plans, and manage test projects according to software requirements.

The main work of software testing is verification and validation.

Verification is a series of activities that ensure that the software is performing some specific function correctly, that is, that the software does the event in the correct way.

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.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.Formal proof of program correctness, that is, the process of using formal theory to prove that the program complies with the provisions of the design specification.

3.Evaluate and report on market evaluation, examination, testing, inspection, auditing, etc., or whether certain processing, 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 specification, outline design document, detailed design document, of course, the main object of software testing is the source program.

Software testingJob description:

1. Use various testing techniques and methods to test and find software defects in the software.

2. The tester will compile the defects found into a formal defect report and submit it to the developer for confirmation and repair of the defects.

3. Testers need to analyze the quality of the software. After the test is completed, the tester needs to analyze the software quality based on the test results, including defect rate, defect distribution, defect repair trend, etc. Specific metrics are given for various quality characteristics of the software, including functionality, reliability, ease of use, security, time and resource characteristics.

4. In order to conduct better and more effective tests and ensure the quality of test work, testers need to design test cases and form test case reports before executing test work.

It is recommended to choose Danai Education for learning software testing.

The institution is committed to the IT Internet industry, training software development engineers, test engineers, UI designers, network marketing engineers, accountants and other workplace talents, with a complete teaching and research team in the industry, strong faculty, to ensure the interests of students, all-round protection of student learning.

If you want to know more about software testing, we recommend consulting Danet Education. The institution has an original teaching system, and the enterprise has a double election meeting. Danai OMO teaching mode, newly upgraded, online and offline interactive learning, benchmarking enterprise talent standards, formulating professional learning plans, including mainstream hot technologies.

Theoretical knowledge + learning thinking + practical operation to create a complete learning closed loop to meet the diverse learning needs of students.

1.Set up a test environment.

2.Write test cases.

3.Execute test cases.

4.Write test plans and test reports.

5.Test and file a bug ticket.

6.Keep track of bug fixes.

7.Automate testing, scripting, execution, analysis, reporting.

8.Performance testing, scripting, execution, analysis, tuning, reporting.

Write a plan. Design use cases.

Perform the test. Test summary.

Software testing is a very common job in our lives, and the demand for software testing talents in the market is also very large, so what is the job content of software testing? Let's take a look.

What does software testing do:

1. Find out the bugs in the developed software through technical testing, that is, find out the defects and deficiencies of the software.

2. After finding out the problems, it is necessary to use industry professional terminology to organize these problems into a standardized problem report, and present the problems to the software developers in detail and professionally.

3. In addition to finding out the problems existing in the software itself, it is also necessary to analyze the quality of the software, and then give suggestions for improving the software from different aspects.

What are the areas of software testing that need to start?

1. Data and database integrity test: Data and database integrity test refers to the test of relational database integrity principles and data rationality test.

3. Functional test: test whether each functional module of the software is correct and whether the logic is correct.

5. Performance test: that is, to test the quality of the software, such as load test, strength test, database capacity test, etc.

6. Security and access control test: the security level of the software program, the security level of the system.

7. Failover and recovery test: When the host software and hardware disaster occurs, the test of whether the backup machine can start normally.

8. Compatibility test: that is, configuration test, the operation of the test object in different software and hardware configurations.

The above is today's sharing, I hope it can help you.

Summary is a written material that reviews and analyzes and evaluates the learning or work situation at a certain stage afterwards, which can help us to find the rules of study and work, so we need to write a summary. So do you know how to write a summary? The following is a summary of the software testing methods I have collected for you, for reference only, I hope it can help you.

I have just completed three months of work, and during these three months, I have mainly done the following work:

1.Familiarity and understanding of the software.

2.Followed the developers to track the improvement of the software, using the method of functional combinations, tested various tools, submitted a total of 405 bugs, and verified 268 closed.

3.A part of the user manual and the administrator's manual of the software was tested and changed, and during this time, the understanding of the various functions of the software was deepened.

Min Hood has basically tested all the functions that have been implemented, and has also put forward its own suggestions for improving the use of the software. During this period, I also learned about the functional requirements of the software, mainly to test the functionality of the client-server side and the solution designer. I learned a lot during this time.

During this period, the software has been continuously improved according to user feedback, basically there will be changes every day, I have been constantly testing according to the progress of development, learning while using the newly added tools, submitting defect reports, and communicating with developers in a timely manner to deal with defect reports with differences, and repeatedly verifying the defects after repair. It wasn't until last week that I took advantage of their travel time to re-test the tools I had previously tested. Through the improvement of this time, the various functions of the software have become more and more comprehensive, and the current software'The basic functions have been implemented, the fatal errors are becoming less and less, and the automated performance testing tool loadrunner has been tried out, because the software is not yet complete, it is difficult to match the protocol in use, and now I am familiar with another automation tool, rationalrobot, to perform performance testing.

In the second half of the year, the main work hours are:

1.As the software progresses, functional testing will be refined and overall testing of other aspects such as performance testing, interface testing, usability and other aspects will be prepared as early as possible.2Test all documentation related to the Software.

3.Resolve all remaining discrepancies in the bug report and perform regression testing with reference to the flawed bug report.

4.As other projects are underway, work begins to prepare for the pre-testing process.

The specific work implementation arrangements will also be adjusted according to the work progress and planning of the project team.