Testing : Error guessing and exploratory testing
2009-07-29 17:53
225 查看
Gieno Testing : Error guessing and exploratory testing | ||
Error guessing and exploratory testing are functional test techniques based on the test engineer’s knowledge, experience, and intuition. The skill in error guessing and exploratory testing is to derive a comprehensive set of tests without missing areas, and without generating redundant tests. Error guessing and exploratory testing are typically viewed as unstructured approaches to software testing. Some people argue that error guessing is not a valid testing technique; however, highly successful testers are very effective at quickly evaluating a program and running an attack that exposes defects. Error guessing is usually most productive in falsification type testing, but when coupled with exploratory testing these techniques can be used to design a set of tests that will uncover errors and successfully validate the product works as expected. Exploratory testing is extremely useful when we are faced with software that is untested, unknown, or unstable. But after the product is more stable and settled, we would like to have a way to ease into a less labor-intensive, hopefully automated, mode of testing. Exploratory testing ventures into the product while it is still in great flux and not yet ready for automation. According to IEEE, exploratory testing is the most widely practiced testing technique. Tests are derived relying on tester skill and intuition, and on the tester's experience with similar programs. More systematic approaches are advised. Exploratory testing might be useful (but only if the tester is really an expert) to identify special tests not easily captured by formalized methods. The fact is that every tester does exploratory testing. For example: When the tester first gets the product, with or without a specification, and tries out the features to see how they work, and then tries to do something “real” with the product to develop an appreciation of its design, this is exploratory testing. When a tester finds a bug, she troubleshoots it a bit, both to find a simple set of reproduction conditions and to determine whether a variant of these conditions will yield a more serious failure. This is classic exploration. The tester decides what to do next based on what she’s learned so far. When the programmer reports that the bug has been fixed, the tester runs the original failure-revealing test to see if the fix has taken. But the skilled tester also varies the regression test to see whether the fix was general enough and whether it had a side effect that broke some other part of the program. This is exploratory testing. | ||
相关文章推荐
- Bit error testing and training in double data rate (ddr) memory system
- 解决 Error: Table './db_name/table_name' is marked as crashed and last (automatic?) repair
- Tuning and Testing Enterprise Web Services with SoapUI and JMeter
- The connection to adb is down, and a severe error has occured.
- The server encountered an internal error or misconfiguration and was ...
- Android程序出错:The connection to adb is down, and a severe error has occured
- DedeCMS Error: (PHP 5.3 and above) Please set request_order
- C语言宏定义(error and pragma)
- Homework9 —— Scenario and persona based Testing
- The connection to adb is down, and a severe error has occured.
- The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access, and has no functional impact
- Finding and fixing the stack overflow at line 0 error
- ERROR 1436 (HY000): Thread stack overrun: 6656 bytes used of a 131072 byte stack, and 128000 bytes
- DedeCMS Error: (PHP 5.3 and above) Please set request_order
- Installing and Testing ON
- cocos2dx android版本移植时的Error format not a string literal and no format arguments解决方案
- The connection to adb is down, and a severe error has occured.
- 总结:SharePoint 2010 -- Error and Solution(2)-- FileNotFoundException was caught
- [Dynamic Language] pyspark Python3.7环境设置 及py4j.protocol.Py4JJavaError: An error occurred while calling z:org.apache.spark.api.python.PythonRDD.collectAndServe解决!
- Guide to Software Testing and Quality Assurance