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
Pairwise Testing
What is Pairwise Testing?
乳制品测试也称为全胎测试,是采用结合法测试软件的一种测试方法。 它为测试所涉参数的所有可能的分离组合提供了一种方法。
假设我们有一套有待测试的软件,其中10个投入领域和10个可能的投入领域,则有10个可测试的投入。 在这种情况下,即使我们希望测试所有组合,也不可能进行详尽的测试。
让我们以一个实例理解这一概念:
Example:
附有10个要素的简单清单箱的申请 (Let s 说0,1,2,3,4,5,6,7,8,9)以及一个检查箱、无线电台、文本箱和K Button。 文本箱的限制是,它只能接受1至100之间的数值。 下面是全球倡议每个目标所能达到的数值:
方框1:
检查箱——检查或检查
Button电台-地址或外国广播公司
文本框: 1至100年
计算出产品B的详尽组合。
List Box = 10 Check Box = 2 Radio Button = 2 Text Box = 100 Total Number of Test Cases using Cartesian Method : 10*2*2*100 = 4000 Total Number of Test Cases including Negative Cases will be > 4000
现在的想法是减少测试案例的数量。 我们将首先努力查明使用常规软件测试技术的案例数目。 我们可以将清单箱值视为0,而其他则认为0既不积极,也不消极。 无线电塔顿和检查箱的数值不能降低,因此其中每个单元的组合将达到2个。 文本箱值可减为3项投入(Vapd Integer、Invapd Integer、Alpha-Special特征)。
现在,我们将计算使用软件测试技术的案例数目,2*2*2*3 = 24(包括负面案例)。
现在,我们仍能够进一步减少这种结合,使之进一步融入全省技术。
Step 1: Order the values such that one with most number of values is the first and the least is placed as the last variable.
www.un.org/chinese/ga/president 清单箱可达到2个数值。
Step 3: 讨论中的下列栏将打上盒子。 再次重申 检查箱可达到2个数值。
Step 4:Now 我们需要确保我们涵盖清单箱和核对箱之间的所有组合。
Step 5:Now 我们将利用同样的战略检查布顿电台。 它可以达到2个价值观。
Step 6: 如果所有乳制品价值都包含在下表中,则予以更正。
Text Box | List Box | Check Box | Radio Button |
---|---|---|---|
Vapd Int | 0 | check | ON |
Vapd Int | others | uncheck | OFF |
Invapd Int | 0 | check | ON |
Invapd Int | others | uncheck | OFF |
AlphaSpecialCharacter | 0 | check | ON |
AlphaSpecialCharacter | others | uncheck | OFF |
Result of Pair-Wise Testing:
Exhaustive Combination results in > 4000 Test Cases. Conventional Software Testing technique results in 24 Test Cases. Pair Wise Software Testing technique results in just 6 Test Cases.Advertisements