<< Exploratory Software Testing >> Chapter II manual Testing

Chapter II Manual Testing

1. Root causes of software defects
This book discusses two types of defects:

A. Programmer introduction B. The operating environment causes

2. Defect prevention and detection
(1) Defect prevention
defect prevention techniques are generally developed from a development perspective, including:

A. Better design specifications B. Is the Time Code review System (code review) c. Run the Code static analysis tool D. Run unit tests ( Unit testing)

all defect prevention technologies have the following fundamental issues:

A. The sub-personnel are bad testers B. Software at rest c. Lack of data

(2) Defect detection
testers typically use two forms of dynamic testing:

A. Automated testing (by writing code to test an application) B. Manual testing (using the program's user interface, manually entering data for testing)

3. Manual Test (manual testing)
(1) using scripts in manual testing:
scripts are used to specify what input values to use, and how to determine the correct software output results.

(2) Exploratory testing:
If the test script is completely thrown away, it is called exploratory testing.
test results, test instances, and test documents are created when you run your tests.
best for Web applications that use the Agile development process (agility method).
the downside is that testers are likely to have no focus in the test. In the absence of a test document, how does the tester guarantee good test coverage?
the importance of guiding methods. From a test strategy point of view, it is equally important to know exactly what to measure and how to measure it.
Two guidance methods: Local exploratory test method (exploratory testing in the small) and global exploratory test (exploratory testing in the large)

a. Local Exploratory testing: assist testers to make decisions in a timely manner during the testing process. b. Global Exploratory testing method: Used to help testers design overall test plans and test strategies.      a single individual test case should overwrite what features of the software?      what software functions must be put together?      be measured first?      how to decide which function to test first, which post-test?      if there are multiple testers in a project, what testing strategy should be used to ensure that the work of each tester complements each other?      for these higher levels of overall testing and testing strategy decisions, how do testers use exploratory software testing method to trade-offs? c. Use both exploratory testing and script testing:       These two methods can be well combined.      use formal scripting to set a clear framework for exploratory testing, which can improve the effectiveness of test script testing Provides a more varied variety of test cases in the script.

<< Exploratory Software Testing >> Chapter II manual testing