Summary
1.1.
介绍
A
2.1.
Acceptance Testing
2.2.
Accessibility Testing
2.3.
Active Testing
2.4.
Actual Outcome
2.5.
Adhoc Testing
2.6.
Age Testing
2.7.
Agile Testing
2.8.
All Pair Testing
2.9.
Alpha Testing
2.10.
API Testing
2.11.
Arc Testing
2.12.
Anomaly
2.13.
Assertion Testing
2.14.
Audit
2.15.
Automated Software Testing
B
3.1.
Backward Compatibility Testing
3.2.
Baseline Artifacts
3.3.
Basis Path Testing
3.4.
Basis Test Set
3.5.
Bebugging
3.6.
Behaviour Testing
3.7.
Benchmark Testing
3.8.
Beta Testing
3.9.
Big-Bang Testing
3.10.
Binary Portability Testing
3.11.
Black box Testing
3.12.
Bottom Up Testing
3.13.
Boundary Testing
3.14.
Branch Testing
3.15.
Breadth Testing
3.16.
BUG
3.17.
Build Validation
3.18.
Business Process
C
4.1.
Capability Maturity Model
4.2.
Capture/Replay Tool
4.3.
Cause-Effect Graph
4.4.
Code Coverage
4.5.
Code Freeze
4.6.
Code Inspection
4.7.
Code Review
4.8.
Code Walkthrough
4.9.
Code Driven Testing
4.10.
Code Free Testing
4.11.
Comparison Testing
4.12.
Compatibility Testing
4.13.
Compliance Testing
4.14.
Concurrency Testing
4.15.
Condition Coverage Testing
4.16.
Configuration Testing
4.17.
Configuration Testing
4.18.
Context Driven Testing
4.19.
Control Flow Path
4.20.
Conversion Testing
4.21.
Correctness
4.22.
Coverage Items
4.23.
Cyclomatic Complexity
D
5.1.
Data Integrity Testing
5.2.
Data Driven Testing
5.3.
Data Flow Testing
5.4.
Database Testing
5.5.
Debugging
5.6.
Decision Coverage Testing
5.7.
Defect
5.8.
Defect Logging and Tracking
5.9.
Defect Life Cycle
5.10.
Delta Release
5.11.
Dependency Testing
5.12.
Depth Testing
5.13.
Destructive Testing
5.14.
Development Environment
5.15.
Documentation Testing
5.16.
Domain Testing
5.17.
Durability Testing
5.18.
Dynamic Testing
E
6.1.
Emulator
6.2.
End-to-End Testing
6.3.
Endurance Testing
6.4.
Entry Criteria
6.5.
Equivalence Partitioning Testing
6.6.
Error
6.7.
Error Guessing
6.8.
Error Seeding
6.9.
Exhaustive Testing
6.10.
Exit Criteria
6.11.
Expected Outcome
6.12.
Exploratory Testing
F
7.1.
Failover Testing
7.2.
Failure
7.3.
Fault
7.4.
Fault Injection Testing
7.5.
Feasible Path
7.6.
Feature Testing
7.7.
Functional Decomposition
7.8.
Functional Testing
7.9.
Fuzz Testing
G
8.1.
Glass Box Testing
8.2.
Globalization Testing
8.3.
Gorilla Testing
8.4.
Grey Box Testing
8.5.
GUI Software Testing
H
9.1.
Harness
9.2.
Heuristics
9.3.
Hybrid Integration Testing
I
10.1.
Implementation Testing
10.2.
Incremental Testing
10.3.
Independent Testing
10.4.
Infeasible Path
10.5.
Inspection
10.6.
Install/Uninstall Testing
10.7.
Integration Testing
10.8.
Interface Testing
10.9.
Internationalization Testing
10.10.
Inter Systems Testing
10.11.
Isolation Testing
10.12.
Issues
K
11.1.
Keyword Driven Testing
11.2.
Key Performance Indicator
11.3.
Known Issues
11.4.
LCSAJ Testing
11.5.
Load Generator
11.6.
Load Testing
11.7.
Localization Testing
11.8.
Logic Coverage
11.9.
Loop Testing
M
12.1.
Maintainability Testing
12.2.
Manual Testing
12.3.
Model Based Testing
12.4.
Modified Condition Coverage
12.5.
Modularity Driven Testing
12.6.
Monkey Testing
12.7.
Mutation Testing
N
13.1.
Negative Testing
13.2.
Non-Functional Testing
O
14.1.
Operational Testing
14.2.
Orthogonal Array Testing
P
15.1.
Pair Testing
15.2.
Pairwise Testing
15.3.
Parallel Testing
15.4.
Partial Test Automation
15.5.
Passive Testing
15.6.
Path Testing
15.7.
Peer Review
15.8.
Penetration Testing
15.9.
Performance Testing
15.10.
Portability Testing
15.11.
Positive Testing
15.12.
Post Condition
15.13.
Pre-Condition
15.14.
Predicted Outcome
15.15.
Priority
15.16.
Process Cycle Test
15.17.
Progressive Testing
15.18.
Prototype Testing
Q
16.1.
Quality Assurance
16.2.
Quality Control
16.3.
Quality Management
R
17.1.
Random Testing
17.2.
Recovery Testing
17.3.
Regression Testing
17.4.
Release Candidate
17.5.
Release Notes
17.6.
Reliability Testing
17.7.
Requirements
17.8.
Requirement Based Testing
17.9.
Requirements Traceability Matrix
17.10.
Result
17.11.
Re-testing
17.12.
Review
17.13.
Risk
17.14.
Risk Management
17.15.
Root Cause
S
18.1.
Safety Testing
18.2.
Sanity Testing
18.3.
Scalability Testing
18.4.
Scenario Testing
18.5.
Schedule
18.6.
Script
18.7.
Security Testing
18.8.
Simulation
18.9.
Smoke Testing
18.10.
Soak Testing
18.11.
Software Requirement Specification
18.12.
State Transition Testing
18.13.
Static Testing
18.14.
Statistical Testing
18.15.
Storage Testing
18.16.
Stress Testing
18.17.
Structural Testing
18.18.
Structural Walkthrough
18.19.
Stub
18.20.
Symbolic Execution
18.21.
Syntax Testing
18.22.
Syntax Integration Testing
18.23.
System Testing
18.24.
System Under Test
T
19.1.
Technical Review
19.2.
Test Approach
19.3.
Test Automation
19.4.
Test Basis
19.5.
Test Bed
19.6.
Test Case
19.7.
Test Case Design Technique
19.8.
Test Suite
19.9.
Test Completion Criterion
19.10.
Test Completion Report
19.11.
Test Completion Matrix
19.12.
Test Data
19.13.
Test Data Management
19.14.
Test Driven Development
19.15.
Test Driver
19.16.
Test Environment
19.17.
Test Execution
19.18.
Test Management
19.19.
Test Plan
19.20.
Test Steps
19.21.
Test Strategy
19.22.
Thread Testing
19.23.
Top Down Integration Testing
19.24.
Total Quality Management
19.25.
Traceability
U
20.1.
Unit Testing
20.2.
Unreachable Code
20.3.
Usability Testing
20.4.
Use Case Testing
20.5.
User Acceptance Testing
20.6.
User Interface Testing
20.7.
V Model
20.8.
Validation Testing
20.9.
Verification Testing
20.10.
Virtual Users
20.11.
Volume Testing
20.12.
Vulnerability Testing
W
21.1.
Web Application Testing
21.2.
White box Testing
21.3.
Workflow Testing
本书使用 LsBook 发布
Expected Outcome
目录
预期结果
预期结果
在测试设计阶段，编写测试用例，使每个案例都具有预期结果，并与实际结果进行比较。如果有偏差，则称为缺陷。
简而言之，在执行测试之前，应记录获得预期结果。
在开发测试用例时，我们通常会有以下字段：
测试场景
测试步骤
参数
预期结果
实际结果
结果匹配 "
"
没有匹配的结果 "
"