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
Test Maturity Model
Test Maturity Model
What is a Test Maturity Model?
测试成熟模式以能力成熟模式为基础,具体规定了一个软件开发组织不断提高的一系列水平。 越高,软件开发过程越好,达到每个层次,便是一个昂贵和耗时的过程。
Levels of CMM:
等级1:初始——软件过程的特点是不一致,有时甚至混乱。 危机期间放弃了既定的程序和标准做法。 本组织的成功在很大程度上取决于个人的努力、才能和英雄。 英雄们最终转向其他组织,利用他们丰富的知识和教训。
Level Two: Repeatable - This level of Software Development Organization has a basic and consistent project management processes to track cost, schedule, and functionapty. The process is in place to repeat the earper successes on projects with similar apppcations. Program management is a key characteristic of a level two organization.
Level Three: Defined - The software process for both management and engineering activities are documented, standardized, and integrated into a standard software process for the entire organization and all projects across the organization uses an approved, tailored version of the organization s standard software process for developing, testing and maintaining the apppcation.
四级:管理 - 管理层可以通过精确测量有效地控制软件开发工作。 就此而言,本组织为软件处理和软件维护设定了量化的质量目标。 在这一成熟水平,利用统计技术和其他定量技术控制流程的运行,在数量上可以预测。
5级:优化——这一级的主要特征是,通过渐进和创新的技术改进,不断改进进程业绩。 在这一层面,进程的变化是改进进程业绩,同时保持统计概率,以实现既定的量化进程改进目标。