Software Testing and Quality Control

The mail functionality in QC (Quality Center) is called a Repository because it stores and manages test artifacts, requirements, and defects in a centralized location. A repository serves as a single source of truth for all testing assets.

Test sets in Quality Center can contain both manual and automated tests, giving teams flexibility to group different test types together for execution cycles.

A test set is a logical collection of tests grouped to achieve a specific testing objective or goal, such as validating a feature or supporting a release cycle.

The testing workflow in Quality Center begins with the Release module, where release cycles are created and the overall testing schedule is defined.

Assigning a status to a defect (New, Open, Fixed, Closed, etc.) tracks its progression through the defect life cycle, recording its current state in the workflow.

Defects can be logged from multiple modules - Requirements (during specification review), Test Plan (during test design), Test Lab (during test execution), and the Defect module itself.

The History tab in the Defect module maintains a complete audit trail of all changes made to a defect, including status updates, field modifications, and comments.

In HP ALM/Quality Center, when a requirement is assigned to a release, it needs to be tested across all cycles to ensure thorough validation. Testing only in one cycle would not provide complete coverage. Testing only in the last cycle would miss early feedback and integration issues. The 'all cycles' approach ensures regression testing and catches defects throughout the release lifecycle.

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.

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.

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.