Types of Testing

In software testing, traceability matrices are categorized as Horizontal (tracing requirements across test cases) and Vertical (tracing requirements through different levels of testing artifacts). 'Diagonal Traceability matrix' is not a standard term - this tests knowledge of actual traceability types versus fabricated options.

Compatibility testing evaluates software behavior across different hardware configurations, software versions, operating systems, and network environments. Install/uninstall testing focus on deployment, while performance testing measures speed and scalability - compatibility is about correct operation across varied environments.

Security testing specifically focuses on evaluating how well a system protects against unauthorized access from both internal and external sources. Stress testing checks system capacity under load, compatibility testing verifies interoperability with other systems, and comparison testing benchmarks against competitors.

Confirmation Testing, also known as Retesting, involves verifying that a defect has been fixed after it was reported. Regression testing checks for new defects in unchanged areas, risk-based testing prioritizes by risk, and comparison testing benchmarks against standards.

Age testing evaluates how software performs as it ages and handles long-term usage, simulating extended operation over time. Ad-hoc testing is informal exploration without documentation, active testing isn't a standard industry term, and API testing specifically tests application programming interfaces.

Acceptance testing verifies that software meets customer and business requirements, typically conducted by customers or end-users before final delivery. Blackbox testing examines functionality without viewing internal code, load testing checks system capacity under stress, and performance testing measures responsiveness.

Smoke testing (also called build verification testing) quickly checks that major functions work without detailed testing, ensuring the build is stable enough for further testing. Regression testing checks for defects in unchanged areas, retesting verifies specific fixes, and unit testing examines individual components.