Software Testing Course Summary

This semester I studied software testing this professional course, although the course is short, but let me benefit. At the end of the semester, I also establish a basic understanding and understanding of this course. Software testing This course, as a very important course in software engineering, has occupied an irreplaceable role in the field of software, and when a software is running on a computer from embryonic to real, no one can guarantee that the computer software can one step meet people's needs. So there is the software test, the purpose is: to confirm the quality of the software, on the one hand is to confirm that the software did what you expect, on the other hand is to confirm the software in the right way to do this event. Below I simply write about this semester's summary and harvest of the course.

Through half a semester of study, let me understand the importance of software testing, but also learned some test methods, such as unit testing, system testing, integration testing and so on. Unit testing is a small piece of code written by a developer to verify that a small, well-defined function of the code being tested is correct. Typically, a unit test is used to determine the behavior of a particular function under a particular condition (or scenario). Unit testing is done by the programmer himself, and ultimately the programmer himself. It can be said that programmers have the responsibility to write functional code, but also have the responsibility for their own code to write unit tests. Performing unit tests is to prove that the code behaves as we expect it to. The primary purpose of unit testing is to address various errors that may exist during the encoding process, such as errors in user input boundary values during validation. The system test is to assemble the tested subsystem into a complete system for testing. It is an effective way to verify that the system is capable of providing the specified function in the system's program specification, and the purpose of the system testing is to test the final software system thoroughly to ensure that the final software system meets the product requirements and follows the system design. Integration testing is a logical extension of unit testing. Its simplest form is: Two tested units are assembled into one component, and the interfaces between them are tested. In this sense, a component refers to an integrated aggregation of multiple cells. In a real-world scenario, many units are assembled into components that are then assembled into a larger part of the program. The method is to test the combination of fragments and eventually extend the process to test your module with the other group's modules. Finally, all modules that make up the process are tested together. I think that in the entire large-scale software engineering, whether it is demand analysis, architecture design, or even the final debug, there are some loopholes, which requires as a software tester to master a wealth of software engineering principles and knowledge. The work of testing will be present throughout the project cycle, that is, when a variety of analytical studies are required at the beginning of the project. Especially when the requirement specification is formed, there is a need to test the document and even lead the whole project.

Test distance, the road long its repair far XI, I will go up and down and quest.

Software Testing Course Summary