Software Testing and Quality Control

HP Quality Center is a web-based test management tool used to manage requirements, plan and schedule tests, execute test suites, and track defects throughout the software development lifecycle.

Tests are linked to requirements within the Requirements module using the Test Coverage tab, allowing users to map specific test cases to individual requirements.

When a defect is valid but cannot be fixed immediately due to a gap in requirements or lack of code/resources, its status is set to 'Deferred' to be addressed in a future release.

Establishing a Traceability Matrix in Quality Center involves linking requirements to tests (Requirements-Test coverage) and analyzing how requirements cover the test plan (Test Plan-Requirement coverage) to ensure full alignment.

In Quality Center (now HP ALM), test cases are executed in the Test Lab module. The Test Lab is specifically designed for test execution, where test sets are created and run. Test Plan is for design, Defects for tracking issues, and Releases for managing release cycles.

A test plan tree can be created by defining test folders and tests manually in the Test Plan module. This hierarchical organization allows grouping tests by subject area, feature, or other criteria. Converting releases or saving automated tests are different workflows.

Requirement traceability is the mechanism used in Quality Center to relate requirements to one another, establishing parent-child or peer relationships to track dependencies.

In the Test Lab module of Quality Center, you use the 'Select Tests' button to open the test plan tree pane, allowing you to select and add test cases from the Test Plan to your execution test sets.

Heinz Kabutz (Java specialist) and Joshua Bloch (Effective Java author) are both strong advocates of unit testing. Both have written extensively about testing best practices. Cay Horstmann is also a Java educator but less associated with unit testing advocacy compared to the other two.

User Acceptance Testing (UAT) is conducted by end-users or customers to verify the software meets business requirements and is satisfactory for actual use. Usability testing focuses on user-friendliness, Scalability testing on performance under load, and Ramp testing on stress limits. UAT is the final validation before production deployment.

Ramp Testing involves continuously increasing an input signal (load, data volume, concurrent users) until the system breaks, establishing the breaking point. Recovery Testing checks system recovery after crashes, Sanity Testing verifies basic functionality after changes, and Scalability Testing measures performance at increasing loads without necessarily breaking the system.

Monkey Testing is ad-hoc, random testing without formal test plans - testers 'monkey around' with the system running random tests to check for crashes. Negative Testing uses invalid inputs, Path Testing covers all execution paths, and Performance Testing measures system responsiveness. Monkey testing is informal and exploratory by nature.

Gorilla testing focuses on testing one particular module or functionality heavily and repeatedly. It is different from installation testing which checks the installation process, exhaustive testing which tests all possible combinations, or end-to-end testing which validates the entire system flow.

Beta testing involves testing the software at the client's site after installation, allowing real users to provide feedback before final release. Compatibility testing checks if the software works across different platforms, ad hoc testing is informal without planning, and accessibility testing ensures usability for disabled users.