Software Testing Fundamentals

In Quality Center and ALM, a Release represents a complete set of changes to one or more applications that are packaged together for distribution. This could be a software version, a patch bundle, or a feature set that moves through the testing lifecycle as a unit. Cycles are subdivisions within releases, while Libraries and Baselines are different QC concepts.

Quality Center provides structured workflow support (clear foundation), seamless information flow between testing stages (requirements to tests to defects), and notification/alerting capabilities based on defect status or test results. These three advantages are core benefits of using a centralized test management system. The integrated workflow and automation capabilities distinguish QC from ad-hoc testing approaches.

Adding parameters to manual test steps in Quality Center allows the same test to be executed with different data values without duplicating the test. This parameterization increases flexibility by enabling data-driven testing, where one test design can cover multiple scenarios through different parameter inputs. The feature is designed specifically to make manual tests more reusable and adaptable.

Quality Center provides multiple views for requirements validation and tracking throughout the testing process. Document View shows requirement details, Coverage View displays which tests cover which requirements, and Coverage Analysis View provides detailed coverage metrics and gaps. Using all three views together ensures comprehensive requirement traceability from definition through test execution.

Quality Center supports bidirectional linking between Requirements and Test Plan modules. Users can navigate to either module and create links to the other, providing flexibility in workflow. This bidirectional capability means requirement-to-test and test-to-requirement links can be established from either starting point, supporting different team workflows and preferences.

Regression testing verifies that new changes don't break existing functionality. It re-runs previously passing tests to ensure system stability. Recursive testing is not standard terminology, Whitebox tests internal structure, and Unit testing focuses on individual components.

AdHoc testing is an unstructured, spontaneous approach that falls under Exploratory Testing. Exploratory testing involves simultaneous learning, test design, and execution without pre-defined scripts. Unit testing is component-focused, Regression verifies stability, and Performance testing measures speed/scalability.

Severity measures the technical impact of a bug on the application - how badly it affects functionality. Priority determines fix order based on business importance. Fixability refers to repair difficulty, and Traceability tracks bug history.

The V-Model (Validation and Verification) requires testing to begin in parallel with development. Each development phase has a corresponding testing phase. Waterfall and Linear models separate testing after development, while Spiral is iterative but doesn't mandate concurrent testing.

In risk management terminology, a mitigation plan is the formal document that outlines strategies to reduce the likelihood or impact of identified risks. Migration plans handle system transitions, master plans are comprehensive project roadmaps, and maintenance plans address ongoing operations; none specifically target risk reduction like a mitigation plan does.

Static testing involves verification of software artifacts without executing the code, including reviews, inspections, and walkthroughs. Validation specifically requires running the code to verify behavior, while sanity testing is a subset of dynamic testing.

In equivalence class testing for a line drawing tool, valid inputs are straight lines of different lengths (including 1 dot-width to 4 inches). A curve is fundamentally invalid because it violates the basic geometric requirement of being a line.

Automation testing is highly suitable when the application is stable, minimizing script maintenance, and for long-term projects with multiple releases to maximize the return on investment. Usability testing requires human observation, and short-term projects make the high setup cost of automation unjustified.

Cyclomatic complexity V(G) is calculated as the number of decision statements (predicate nodes) plus one, or more formally E - N + 2P for a connected graph. It measures program control flow complexity and the minimum number of test paths needed.

A Test Incident Report documents any unusual event during testing that requires investigation - such as defects,环境 issues, or unexpected behaviors. A test log is a chronological record, test cycle is a testing iteration, and test item refers to the software component being tested.

The requirements phase serves multiple purposes: understanding user needs (discovery), freezing requirements to establish scope baseline, and defining what needs to be tested. All these activities are integral to requirements gathering. A successful requirements phase accomplishes all these objectives to ensure clear project direction.

Software testing typically accounts for 40-50% of total software development costs according to industry studies and research. This includes activities like test planning, test design, test execution, and maintenance of test artifacts. The 10-20% range underestimates testing effort, while 70-80% and 5-10% are outside realistic industry ranges.

A reliable system is one that is unlikely to cause failure during operation. Reliability in software engineering is defined as the probability of failure-free operation over a given time period in a specified environment. Being completed on schedule (A) is about timeliness, being fault-free (C) is about correctness rather than reliability, and being liked by users (D) relates to usability.

Testability characteristics include Operability (ease of operating the system), Observability (ease of seeing results), Simplicity (ease of understanding), and also Controllability and Understandability. Robustness is a separate quality attribute that describes a system's ability to handle errors and unexpected inputs, not a characteristic of testability itself. A robust system might actually be harder to test because it handles errors gracefully.

Cyclomatic complexity is a white-box testing method used to measure the number of linearly independent paths through a program's source code. It requires examining the internal structure of the code (control flow graph), which is the defining characteristic of white-box testing. Black-box testing (B) focuses on inputs and outputs without examining internal structure, while green-box (C) and yellow-box (D) are not standard testing methodology classifications.