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
Adhoc Testing
What is Adhoc Testing?
如果软件测试没有适当的规划和文件,据说是Adhoc检测。 除非我们发现这些缺陷,否则这种试验就只进行了一次。
申请经过正式测试后,测试完成。 替代方法是最不正规的检测类型,因为NOT是一种结构化的做法。 因此,使用这种方法发现的缺陷难以重复,因为没有符合这些假设情况的测试案例。
测试是在检测员不遵循规格/要求的情况下随机进行应用和检测器测试的情况下进行的。 因此,Adhoc检测的成功取决于检测员的能力,检测员进行检测。 检测员只能根据检测师的直觉,在没有适当规划和文件的情况下发现缺陷。
When to Execute Adhoc Testing ?
如果时间有限,无法进行详尽的测试,通常在正式试验执行后进行。 只有在检测员深入了解试验系统的情况下,检测才会有效。
Forms of Adhoc Testing :
Buddy Test: 两个博客,一个来自发展小组,一个来自测试小组,它们共同确定同一单元中的缺陷。 佛教测试有助于测试者开发更好的测试案例,而发展小组也能够尽早改变设计。 这类测试通常是在完成单位测试之后进行的。
乳房检测: 有两个测试者被分配到相同的模块,他们分享想法,并在相同的系统中开展工作,以发现缺陷。 一名检测员进行测试,另一名检测员记录其调查结果的说明。
Various ways to make Adhoc Testing More Effective
Divide and Rule: 通过逐个测试申请部分,我们将更加关注和更好地理解任何问题。
确定关键功能: 测试员在设计测试案例时,应瞄准NOT覆盖的地区。
www.un.org/Depts/DGACM/index_spanish.htm 也可通过使用简介员、夸张甚至任务监测员将缺陷带入电灯。 因此,在使用这些工具方面是有缺陷的。
文件 调查结果: 尽管测试是随机进行的,但如果时间允许,最好记录检测结果,如果发现偏离情况的话。 如果发现有缺陷,就会产生相应的测试案例,以帮助测试者重新测试假想。