Thinking back to the first lesson, there is a picture that still makes me remember
Yes, I still have a deep impression of the picture, and I give a definition of software testing for most people, including those of us who are learning to write software.
However, after a period of study, some things also gradually understand, why we want software testing.
Software is a tool, but the creator and the user have a great but not. Whether it is a client's needs or a program written for its own purposes, the writer is only an individual, and the assumptions about the use of the software are very flawed, even in the writer's view, and some of the usage issues are transparent and imperceptible to him. Several people write software, users are far greater than this number, and in the course of use, the actual situation will be numerous. Therefore, the black box test, also known as functional testing, for the software functional requirements of the design of the test, in such an environment also changed very important.
But, as I said at the beginning, the black-box test looks like a "use", a lot of a wide range of "use." We still don't know what data we're outputting and what changes have taken place within the software. It's like we've made a leap year query software that can do this successfully, but who knows how the software does it? is calculated based on leap year rules? Or is it hard to keep a record of all the years? Enter what returns what? Functionally identical software differs in both implementation and performance. This is only in terms of users, for the designer, the software also has a lot of work to upgrade and maintenance and so on. The refurbishment machine also needs to be disassembled, how does the software really test maintenance? The test of the structure, that is, the white box test.
Software is a tool, a tool written by software designers. They replace a lot of work that needs people to do. However, the tools are good or bad, write high-quality and efficient software is the programmer's goal. Not only with a use, found that no problem on the release, such a product is not a good product, not responsible for the practice. Just a few weeks of study can not be more in-depth understanding of software testing deeper things, this is also in the future study work needs to devote energy, continue to understand a science.
End of software Testing Course Summary