Practical Software Testing Guide (Electronic Industry Press)-Reading Notes 1

Today, a good friend of junior high school, Wang Wei, accompanied her boyfriend to come to Dalian for an interview. She hasn't seen her for several years and misses me very much.
I arrived at the train station when I had lunch with my roommate after my tutor's class in the morning. But I was late and asked them to wait for a meeting. Fortunately, I found them right away, and she remained unchanged, seeing her reminds me of the wonderful memories of my junior high school, it is indeed a wonderful time second only to that of my junior high school students. Of course, it is not a complaint that I have never been happy before, it was just that the carefree and carefree life that was also favored by teachers and classmates was really good. It seems like it's time to stop. You can recall the past, but you can't live in the past.

Let's get down to the truth and start reading notes today. It divides all the chapters of the book into three parts, which are listed as follows:

Part 1 Introduction
Chapter 1 fault models for Software Testing
This chapter describes how to consider software behavior. A new idea of software behavior: By understanding what the software is doing, we can understand how to make it wrong. This person is called a fault model.

Part 2 User Interface attacks
Chapter 2 test user interfaces: Input and Output
This chapter is suitable for black box testing.
Chapter 3 test user interfaces: Data and computing
This chapter contains "gray-box testing" because of problems between black-box testing and white-box testing. The focus of a specific attack is to destroy data and computing constraints.

Part 3 system interface attacks
Chapter 4 test the file system interface
When interacting with data files, the software fails. This chapter focuses on the problems and solutions for testing file systems.
Chapter 5 software/operating system interface Testing
Software often uses other software to do some work for it. When external software resources fail or behavior is abnormal, our own software will also be damaged. Test Problems related to application interoperability.

Conclusion
Chapter 6 parting advice
It is not a skill or technology that makes a great test team

I hope that I can read the following chapters in the next week. I feel that some of the content is not suitable for me, a newbie who tests the zero-Foundation program. But I have already started to read it. I should have some gains.