15. Explore It! In-depth understanding of exploratory software testing

1) Testing a lot of thinking not only applies to the work is also applicable to life, and that moment, in front of her, I have flinched. Elisabeth the agility test with her passion and professionalism, which earned her the 2010 Agile Alliance Gordon Pask Award, which was set up to honor people like her who have made an outstanding contribution to agile practice. 2) Exploratory testing is important. While applying this approach to any kind of development can produce value, it is best suited to agile development that is common in fast-cycling and sudden-change situations. There's a lot in common with the methods of development and testing. 3) It's so disappointing, no matter how many tests we write, or how many test cases we execute, the most serious flaws are found only when you deviate from script execution. "4) Explore this matter, its outcome may be completely open-ended. If you do not use some mechanism to arrange and organize the work, then you are likely to take the software blindly, spend hours or days of time, the results can not find any relevant or useful information, no sharing. Jon Bach and James Bach put forward a test management (SBTM) practice based on probing sessions to solve the problem. This practice sets the time in the form of a timed probing session sequence, and establishes the focus for the probing session in advance. (the 2nd chapter describes how to identify and capture this focus.) Throughout the exploration session, you explore, design and perform tests, from one experiment to the next without pausing. 5) During the probing session, you need to make a record so that you know what you have explored and what information you have found. Of course, you can use your records yourself. When you have a brief report with the stakeholders, you can refer to the use of these records, but they are not the same as the traditional test or test report. This original ecological record is of limited value to others, primarily to assist in documenting test ideas, problems, risks, surprises, and other areas you want to explore, as well as bugs. After the probe session is over, you have to capture information that needs to be conveyed to others. You can write down the capabilities and limitations of the explored areas you have observed, or simply sit by the stakeholders and tell them what you have discovered. If you find a bug that needs to be reported, report it. If you have questions in mind, find out who can answer these questions. The probing session provides a regular resting point so that you can summarize the refinement of the survey, and carefully consider what the best areas to explore next. 6) Explore this matter, its outcome may be completely open-ended. If you do not use some mechanism to arrange and organize the work, then you are likely to take the software blindly, spend hours or days of time, the results can not find any relevant or useful information, no sharing. Jon Bach and James Bach put forward a test management (SBTM) practice based on probing sessions to solve the problem. The practice is to schedule time in the form of a timed detection session sequence,Set the focus for the probing session. (the 2nd chapter describes how to identify and capture this focus.) Throughout the exploration session, you explore, design and perform tests, from one experiment to the next without pausing. 7) During the probing session, you need to make a record so that you know what you have explored and what information you have found. Of course, you can use your records yourself. When you have a brief report with the stakeholders, you can refer to the use of these records, but they are not the same as the traditional test or test report. This original ecological record is of limited value to others, primarily to assist in documenting test ideas, problems, risks, surprises, and other areas you want to explore, as well as bugs. After the probe session is over, you have to capture information that needs to be conveyed to others. You can write down the capabilities and limitations of the explored areas you have observed, or simply sit by the stakeholders and tell them what you have discovered. If you find a bug that needs to be reported, report it. If you have questions in mind, find out who can answer these questions. The probing session provides a regular resting point so that you can summarize the refinement of the survey, and carefully consider what the best areas to explore next. 8)   A simple three-segment template: • Goal: Where do you want to explore? It may be a feature, a requirement, or a module. • Resources: What resources do you need to bring with you? Everything is a resource: A tool, DataSet, technology, configuration, or some interdependent feature. 10) A simple three-segment template: • Goal: Where do you want to explore? It may be a feature, a requirement, or a module. • Resources: What resources do you need to bring with you? Everything is a resource: A tool, DataSet, technology, configuration, or some interdependent feature. • Info: What kind of information do you want to find? Do you want to characterize the system in terms of security, performance, reliability, capacity, availability, or any other aspect? Do you want to check the consistency of their design or a standard violation? One)   quality detection regulation a high-quality exploration Charter provides direction without excessively thinning the test behavior. In turn, the detection Charter is too broad and risky, and may not provide enough attention. If the target is too big, it's hard to tell if you've done the exploration. A high-quality exploration Charter is a cue signal: it points out the source of inspiration and avoids the requirement to make a detail of the action or result. 12) There are two main reasons why old habits are hard to break: you may not even realize that you are acting out of habit, and you will feel comfortable even if you are aware of the existence of your habits. However, if you want to be productive, you have to go where you haven't been. There is a way to break the habitual impulse, which is to allow yourself to accept the guidance of randomness. The "noun and verb" technique provides a way to introduce randomness into the software interaction process. The first step in adopting this technique is to put the nouns in the systemand verb recognition. Imagine that you are testing a mail client. Then, the system of nouns or things may include "mail, attachments, contacts, accounts and folders," and so on. The corresponding verb or action may include "Create, send, edit, forward, copy, delete, move." "Random combination test 13)GugaullThe natural Number 10 (100), or 1 followed by 100 0, was created in 1938 by the nephew Milton Siroti of the American mathematician Edward Casna, mainly to delineate the difference between an unimaginable large number and infinity. Refer to https://zh.wikipedia.org/wiki/gugaull. --Translator Note 14) draw a state model and use heuristics to expose those time-related surprises have you ever encountered a situation where a failure is extremely difficult to reproduce? Perhaps what you see is a catastrophic error that happens very accidentally, or you accidentally step on the damaged data, so you can't trace the root of it. This flaw is triggered, often by coincidence of a short period of vulnerability, at which moment everything is ready to go wrong. The software performs a write operation and the file is locked. When you try to access secure Content, the session has timed out. A rare race condition occurs when a part of the system tries to update a record, while another part is still not finished creating the record. These situations are often short-lived and difficult to spot. You may not know how to consciously trigger them, or you can't use them because you don't know how to tell them whether they appear or not. If you don't perceive this vulnerability, it can become frustrating to try to find or reproduce a defect. Fortunately, there is a systematic way to discover and exploit these fragile periods with state models. In this chapter, you'll learn how to draw a state model and use heuristics to expose surprises that are relevant to time.

15. Explore It! In-depth understanding of exploratory software testing