Software Testing Dictionary
A
B
C
D
E
F
G
H
I
K
L
M
N
O
P
Q
R
S
T
U
V
W
Useful Resources
Selected Reading
A
- Automated Software Testing
- Audit
- Assertion Testing
- Anomaly
- Arc Testing
- API Testing
- Alpha Testing
- All-pairs Testing
- Agile Testing
- Age Testing
- Ad Hoc Testing
- Actual Outcome
- Active Testing
- Accessibility Testing
- Acceptance Testing
B
- Business Requirement
- Business Process
- Build Validation
- Bug
- Breadth Testing
- Branch Testing
- Boundary Testing
- Bottom Up Testing
- Black box Testing
- Binary Portability Testing
- Big-Bang Testing
- Beta Testing
- Benchmark Testing
- Behavior Testing
- Bebugging
- Basis Test Set
- Basis Path Testing
- Baseline Artifacts
- Backward Compatibility Testing
C
- Cyclomatic Complexity
- Coverage Items
- Correctness
- Conversion Testing
- Control Flow Path
- Context Driven Testing
- Conformance Testing
- Configuration Testing
- Condition Coverage Testing
- Concurrency Testing
- Compliance Testing
- Compatibility Testing
- Comparison Testing
- Code Free Testing
- Code Driven Testing
- Code-Based Testing
- Code Walkthrough
- Code Review
- Code Inspection
- Code Freeze
- Code Coverage
- Cause-Effect Graph
- Capture/Replay Tool
- Capability Maturity Model
D
- Dynamic Testing
- Durability Testing
- Domain Testing
- Documentation Testing
- Development Environment
- Destructive Testing
- Depth Testing
- Dependency Testing
- Delta Release
- Defect Life Cycle
- Defect Logging and Tracking
- Defect
- Decision Coverage Testing
- Debugging
- Database Testing
- Data Flow Testing
- Data Driven Testing
- Data Integrity Testing
E
- Exploratory Testing
- Expected Outcome
- Exit Criteria
- Exhaustive Testing
- Error Seeding
- Error Guessing
- Error
- Equivalence Partitioning Testing
- Entry Criteria
- Endurance Testing
- End-to-End Testing
- Emulator
F
- Fuzz Testing
- Functional Testing
- Functional Requirements
- Functional Decomposition
- Feature Testing
- Feasible Path
- Fault injection Testing
- Fault
- Failure
- Failover Testing
G
H
I
- Issues
- Isolation Testing
- Inter Systems Testing
- Internationalization Testing
- Interface Testing
- Integration Testing
- Install/Uninstall Testing
- Inspection
- Infeasible Path
- Independent testing
- Incremental Testing
- Implementation Testing
K
L
M
- Mutation Testing
- Monkey Testing
- Modularity Driven Testing
- Modified Condition Testing
- Model Based Testing
- Manual Testing
- Maintainability
N
O
P
- Prototype Testing
- Progressive Testing
- Process Cycle Test
- Priority
- Predicted Outcome
- Precondition
- Post Condition
- Positive Testing
- Portability Testing
- Performance Testing
- Penetration Testing
- Peer Review
- Path Testing
- Passive Testing
- Partial Test Automation
- Parallel Testing
- Pairwise Testing
- Pair Testing
Q
R
- Root Cause
- Risk Management
- Risk
- Review
- Retesting
- Result
- Requirements Traceability Matrix
- Requirements Based Testing
- Requirements
- Reliability Testing
- Release Note
- Release Candidate
- Regression Testing
- Recovery Testing
- Random Testing
S
- System Under Test
- System Testing
- System Integration Testing
- Syntax Testing
- Symbolic Execution
- Stub
- Structured Walkthrough
- Structural Testing
- Stress Testing
- Storage Testing
- Statistical Testing
- Static Testing
- State Transition
- Stability Testing
- Software Requirement Specification
- Soak Testing
- Smoke Testing
- Simulation
- Security Testing
- Script
- Schedule
- Scenario Testing
- Scalability Testing
- Sanity Testing
- Safety Testing
T
- Traceability
- Total Quality Management
- Top Down Integ. Testing
- Thread Testing
- Test Tools
- Test Strategy
- Test Steps
- Test Plan
- Test Maturity Model
- Test Management
- Test Execution
- Test Environment
- Test Driver
- Test Driven Development
- Test Data Management
- Test Data
- Test Completion Matrix
- Test Completion Report
- Test Completion Criterion
- Test Suite
- Test Case Design Technique
- Test Case
- Test Bed
- Test Basis
- Test Automation
- Test Approach
- Technical Review
U
- User Interface Testing
- User Acceptance Testing
- Use Case Testing
- Usability Testing
- Unreachable Code
- Unit Testing
V
W
Useful Resources
Selected Reading
- Who is Who
- Computer Glossary
- HR Interview Questions
- Effective Resume Writing
- Questions and Answers
- UPSC IAS Exams Notes
State Transition
State Transition Testing
What is State Transition Testing?
国家过渡测试是一种黑箱检测技术,通过改变输入条件或改变系统状况,可以产生产出。 换言之,测试旨在实施有效而无效的国家过渡。
When to use?
当我们有一系列事件和适用于这些事件的相关条件时
如果某一事件的适当处理取决于过去发生的事件和条件
它用于与不同国家和所涉过渡有关的实时系统。
Deriving Test cases:
理解各种州和过渡,标明每个有效而无效的国家
确定导致允许的结束状态检验的事件顺序
应指出,所访问的国家和渗透的过渡中,每一个国家都应缩小。
在访问所有国家和所有过渡阶段之前,应重复步骤2和3。
要想使测试案例覆盖良好,就必须产生实际投入价值和实际产出价值。
Advantages:
允许测试者熟悉软件设计,并使他们能够有效地设计测试。
它还使测试者能够覆盖无计划或无效的国家。
Example:
下表显示系统的过渡:
这些测试来自上述州和过渡阶段,以下是需要测试的可能情景。
Tests | Test 1 | Test 2 | Test 3 |
---|---|---|---|
Start State | Off | On | On |
Input | Switch ON | Switch Off | Switch off |
Output | Light ON | Light Off | Fault |
Finish State | ON | OFF | On |