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
Age Testing
Age Testing
What is Age Testing?
这是一种检测技术,评价一种系统今后能够运行的能力,通常由测试小组进行。 随着该系统的老化,在年龄测试中衡量的绩效可能下降的程度如何。
让我们也理解残疾年龄的概念。 衡量标准分两个参数:
1. Phases 2. Time
Defect Age - Phases:
各个阶段的衰弱年龄被定义为注射阶段和缺陷检测阶段之间的差别。
Parameters:
1. 缺陷注入阶段是软件开发周期引入缺陷时的阶段。
2. 缺陷检测阶段是软件开发寿命周期的阶段,而缺陷被确定。
Formula:
Defect Age in Phase = Defect Detection Phase - Defect Injection Phase
Example:
考虑,SDLC 我们采用的方法分为以下几个阶段:
1. 导言 所需经费
2. 设计
3. 。 编码
4. 第四条第4款 单位:千美元
5. 一体化测试
6. 任务 系统测试
7. 基本生活 接受测试,如果在单位测试(4个)中发现有缺陷,并在发展的设计阶段(2)中引入缺陷,那么感染年龄为(4)-(2)=2。
Defect Age - Time:
缺陷年龄的定义是,如果发现缺陷的日期与目前的日期之间有时间差异,则缺陷依然存在。
Parameters:
1. 导言 缺陷在“开放”和“签署”地位和“新地位”中。
2. 结 论 因“不可再使用”或“复制”而处于“封闭状态”的后果是NOT。
3. 。 日数或小时的差额,从起步日期和当日计算。
Formula:
Defect Age in Time = Defect Fix Date (OR) Current Date - Defect Detection Date
Example:
如果发现有缺陷,则在2008年5月5日/10:00时 直至2013年5月23日(12:00 PM)结束,将按以下方式计算出“不满年龄”。
Defect Age in Days = 05/05/2013 11:30:00 AM - 23/05/2013 12:00:00 PM Defect Age in Days = 19 days
Outcome:
为了评估每个阶段的有效性和任何审查/测试活动,降低缺陷年龄,提高成效。
Advertisements