Software Testing and Quality Control

Ad-hoc frameworks have three key characteristics: (A) Some data in datasheet but not truly data-driven, (B) Test steps embedded in Action scripts (high maintenance, low reuse), and (C) Reactive scripting for single issues. These describe poorly structured automation. Option D (None) is incorrect because A, B, and C all accurately describe ad-hoc framework traits.

Test Script Modularity framework emphasizes creating small, independent, reusable script modules (B) which improves maintainability (A) and uses abstraction layers to hide components (D). It does NOT heavily depend on datasheets for each execution - that describes a data-driven framework.

Data-Driven Framework separates test data from test logic - input/output values come from data files (A), and only test data resides in those files (D). Test logic remains in scripts, making B false. Keywords are central to keyword-driven frameworks, not data-driven (C false).

A hybrid framework combining Keyword and Data Driven approaches allows test cases (keywords/steps) and test data to be stored together in external data files, separating test logic from the execution engine.

Data-driven testing has maintainability challenges (A) because each test case needs separate data files. Finding specific data files (B) is difficult as test suites grow. Error tracing (D) is harder during unattended runs, especially when recovery scenarios activate. Extensibility (C) isn't inherently worse - scripts can be as extensible as other frameworks.

Keyword Driven Frameworks make tests readable like manual test cases (A true). They don't require extensive tool training because testers only need to learn keywords, not the underlying tool (B false). The test plan can indeed be structured in spreadsheets with input and verification data (C true). Testers primarily learn keywords and the test plan format (D true). Options A, C, and D are correct.

A Hybrid Framework combines multiple framework types (B true). It includes core components like Data Driven Engine, Component Functions, and Support Libraries (C true). The App Map bridges the automation framework with the application being tested (D true). Option A is incorrect because hybrid frameworks are widely used, not limited.

Mercury (HP) QTP was built on the fundamental Record & Playback capability. While Mercury later promoted Keyword Driven Framework as the best practice, the question asks what framework they 'modeled' - referring to the core automation approach built into the tool itself. The most basic framework type is Record & Play, which captures user interactions exactly as performed.

Test Automation Frameworks are designed to be tool-independent in their architectural principles. A framework provides structure, methodology, and organization patterns that can work across different automation tools. While implementation may use specific tools, the framework concept itself is about methodology and best practices, not tool dependency.

The two methods are 'Convert Requirements to Tests' (batch conversion) and 'Generate a Test from Requirements' (individual test creation). Options B and D use 'Convert a Test' which is backward - you don't convert tests from requirements. Option C reverses the direction.

Within the Requirements module, traceability links are created between requirements (parent-child relationships). Test Cases, Tests, and Defects belong to other modules and are linked differently through cross-module traceability.

Quality Center assigns .jpg extension to screenshots and images uploaded to the system. While .jpeg is technically the same format, QC specifically uses the .jpg extension in its naming convention.

Comparing the defect counts: Test Object A has X defects, B has 145% of X (1.45X), and C has 120% of X (1.20X). Since Test Object B has the highest number of defects (1.45X > 1.20X > X), it potentially has more undiscovered issues and should be given more testing attention.

Testing should be stopped when the predefined exit criteria are met, which typically include coverage metrics, defect density, and schedule constraints. Stopping based solely on project manager decisions, budget depletion, or finding no more defects is subjective and does not guarantee quality.

In Informatica PowerCenter, Gateway Service and Log Service are classified as Core Services that run on every node in the domain to manage basic node operations and logging.