Subversion perfect software: software testing need to know a few things (study notes 1)

  Learned from the author's preface, this book is a wide range of audience, it may be testers, developers, customers and managers. So what is it as their own and want to get this book?

  I think we need to answer this question, you first need to know why the author to write such a book, only to know the purpose of writing this book, you can get the knowledge you want from this book.

  Because there are a lot of people around, and even some managers of related products, will have a lot of illusions and expectations for software testing. To get rid of these misconceptions and ignorance, to write this book is to let more people know about the test, and more rational look at the test. As the authors put it, this book can help different people, including testers, developers, customers, programmers and managers.

  The book written by the author, is writing to questions by way of solutions. On each chapter or section, we will ask questions, and then to answer these questions in the text.

  On the question raised as follows:

  1, Why Test? (Chapter 1)

    In this chapter, the author describes the four test reasons, then every reason to interpret Finally, the author has listed some frequently asked questions (these issues are also bright spots) test.

  2, the test can not do those things? (chapter 2)

    This chapter convergence previous chapter Reasons for testing, but also testing in the project is not a panacea, by testing, there are many failed to do. Of course, the last of frequently asked questions, also worth considering.

  3, why not an exhaustive test? (Chapter 3)

    This chapter describes the reason for not testing all possibilities for managers and testers should understand the test is a sampling process, need to understand the risks to the test sample brought.

  4, test and modify the software BUG What is the difference? (Chapter 4)

    Test can not be defined properly, it may result in endless debate. Let testers or developers do not know what the nature of their work, but also lead to the failure of the project.

  5, meta-information about the quality of software products have? (Chapter 5)

    The purpose of software testing is to provide information about the quality of products, this chapter provides a lot of meta information that caused the failure, by observing and identifying meta information, can significantly improve the efficiency of testing and reduce costs.

  6, information on how to deal with different people because of fear of immune phenomenon caused due? (Chapters 6 and 7)

    When people fear, we will conduct the defense. Testing is easy touches people's fear point, we have to do is to identify defensive behavior exhibited by each person, and then take the initiative to deal with, so as to avoid confusion and emotional impact testing.

  7, a good test is what? (Chapters 8 and 9)

    Good test can not be confirmed. But we can in many ways, not to know or estimate what kind of test. Identify the major misunderstanding about the test, you can better test.   

  8, how to refute the test is keyboarding behavior? (Chapter 10)

    Typing on the keyboard behavior is not a test, then what kind of behavior is the test? This chapter explain to you.

  9. A model of software testing to improve communication problems (12, 13 and Chapter 14)

    This part describes the Satir Interaction Model: ingestion -> determine the meaning -> OK importance -> respond to address issues related to software testing and project to promote the process.

  10, how to make software easier to test and more likely to succeed? (Chapter 15)

    When a project fails, the next need to consider how a project should be improved. This chapter describes several software easier to test and make it easier to succeed.

  11, a number of recommendations on technical review (Chapter 16)

    As soon as possible and the project technical review as often as possible, to test the product, you can reap unexpected benefits.

  12, in which the test by someone else and brought their own fraud? (Chapter 17 and Chapter 18)

    When they want to quickly remove defects and delivery of products, paying particular attention to someone else recommended test tool, this tool is probably a fraud. When we hope everything goes well, it could also cheat on their own kind.

  

Guess you like

Origin www.cnblogs.com/chengabc/p/11552335.html