Exploratory software Test _ Test series

Excerpt highlights 1) behind most of the great ideas lies a graveyard of immature ideas. 2 The user in the purchase function is also suffering from defects 3 special defects: Escape all kinds of detection means and eventually exist in the release of the product defects;
Reason: Manual tests are devoid of purpose, strong randomness, repetition is strong; the consequence of defect: customer churn; 4) 2 Kinds of defects: defects caused by programmer introduction and defects due to running environment, 5 defect Prevention (unit test, code review, etc.) and defect detection; 6 The perspective of developers and test developers: writing Programs , they are bound to have blind spots. --How to implement this function
Tester's perspective: avoid the stereotype of developers. --How to prove that the function can work under limited conditions (different from the programmer's "second pair of Eyes")
(Testers: PM, dev Team change, product quality stability)
7 test-driven development;
Unit test--format, data validation, exception conditions---Use-case review and more early consideration; 8 defect Detection:
Two forms of dynamic testing: Automated testing (excessive reliance on automated testing will bring pitfalls to the eventual success of the program) + Manual testing (user interface, manual input of data, playing a human
Subjective initiative, the design of a real user situation, can identify the obvious defects and imperceptible defects.
9)
If you want to find the application business logic (user needs, often very complex, need manual testing, where the use of automation, the general effect is not ideal) related to the defect---manual testing is the ideal choice.
The best way to detect software defects is to use test techniques, rather than developing technology (too many factors, scenarios that can cause automated tests to fail, and cannot be traced, which requires "human brain" intervention).
10)
The best calculation in the field of manual testing: Exploratory testing (carefully planned test---) set aside time to improvise tests
Common test: test plan prepared in advance;
Exploratory testing: Creating, testing instances, and testing documents when running tests; 11 The most practical scenario for exploratory testing: Web application reasons for Agile development: short Development cycles + no time to write test scripts + function changes quickly (a use case quickly expires, no need to write it);
12 Exploratory flaw: QA may not have an emphasis
13 The two guiding methods of exploratory testing:
Local exploratory testing: making decisions in the process of QA testing
Global Exploratory testing: QA design overall test plan and test strategy
14 Error handling code: Most developers do not like to write, more emphasis on the normal logic function processing;