Software Testing Types & Quality Center Fundamentals

In hierarchical requirement management tools (like HP ALM / Quality Center), linking a child requirement to a test automatically links its parent requirement to ensure proper traceability and coverage rollup.

In HP ALM/Quality Center, when you log a defect during manual test execution, it is automatically linked to the test instance from which it was created. This indirect link maintains traceability between defects and test execution. The defect is not linked to only one entity - it has associations. No separate linking is required as the system handles it automatically. It's not directly linked to other defects, but to the test instance.

HP ALM/Quality Center Excel import macros support importing core test data: requirements (option E), defects (option A), and test plan data (option C) including test cases and steps. Test set data (option B) and Release data (option D) are not typically importable via Excel macros - these have complex hierarchical structures and relationships that are better managed through the UI or API.

A single requirement can have multiple defects associated with it, as multiple issues might be found during the testing or implementation of that requirement.

In QC/ALM, when you delete a folder, it moves to the Unattached folder where it can be recovered. The Unattached folder acts as a temporary holding area for deleted items before they are permanently removed. The Deleted folder typically contains items that are permanently deleted and cannot be recovered.

In QC/ALM, a test set can contain both manual and automated tests. Test sets are designed to be flexible containers that can organize different types of tests together. You can mix manual and automated tests within the same test set for comprehensive test execution and reporting.

Quality Center (QC) is fundamentally a test management repository that stores and organizes test artifacts including test cases, requirements, and defects. Its primary functionality is to serve as a centralized storage and management system for all quality assurance processes and artifacts.

Inspections are formal reviews led by a trained moderator following a documented process with specific roles. Walkthroughs are informal meetings led by the author to present work and gather peer feedback. In inspections, the author typically presents but doesn't facilitate the discussion.

Software incident reports document defects with factual information: who reported it, software version, and actual vs. expected results. They describe what went wrong, not how to fix it - determining the solution is a separate debugging task for developers.

The test case specification defines test inputs, execution conditions, and expected results. Test design specification outlines the overall test approach, test procedure specification details execution steps, and test results document actual outcomes from test execution.

Coverage measurement tools help developers identify which code paths haven't been executed. Dynamic analysis tools detect runtime issues like memory leaks. Performance testing typically requires QA specialists, test comparators serve testers, and incident management is used across the team.

Static code analysis examines source code structure to identify issues like unreachable code, unused variables, and insufficient comments. It cannot detect faults in requirements because requirements are not code - they are separate documents that static analysis tools don't process.

Ad Hoc testing is unstructured, exploratory testing where testers randomly try various functionality to find unexpected defects. Boundary testing checks edge values, Functional testing validates requirements, and Mutation testing modifies code to verify test suite quality. 'Breaking the system randomly' is the hallmark of Ad Hoc.

Endurance testing (also called soak testing) evaluates system stability over prolonged periods to detect issues like memory leaks, resource exhaustion, or slow degradation that only appear after extended runtime. Ad Hoc is random exploration, Compatibility checks cross-platform behavior, and Functional testing validates features.

Agile Testing is a practice in agile development where testing is integrated throughout the development lifecycle, with development treating testing as its customer and emphasizing test-first design through techniques like TDD. It promotes continuous testing alongside development rather than as a separate phase.

Acceptance testing is performed by customers or users to verify if the software meets business requirements and is ready for deployment. Agile testing is a development methodology, functional testing focuses on feature correctness, and smoke testing verifies basic build stability rather than final acceptance.

Exhaustive Testing aims to test every possible combination of inputs and preconditions. While theoretically complete, it's usually impractical for real-world systems due to the exponential growth of test cases with each input variable.

Smoke testing is a preliminary testing cycle designed to ensure that the basic and most critical capabilities of a software application function correctly before proceeding to deeper test suites. Distractors like regression, functional, or component testing refer to more structured, targeted, or comprehensive testing methods.

Soak testing involves running a system under high load for an extended period to identify issues like memory leaks, performance degradation, or resource exhaustion that only appear over time. It helps ensure system stability during prolonged operation.

Stress Testing pushes a system beyond its specified limits to determine breaking points and observe failure modes. It helps identify the maximum load capacity and how the system degrades or fails under extreme conditions, unlike normal load testing which stays within specifications.