testing Online Quiz - 43

Load testing tools automate performance testing, reducing manual effort and allowing simulation of thousands of users from minimal hardware. While commonly applied to web applications, they can test any system, making all three statements valid.

To solve this question, the user needs to know about the objectives of reviews, static analysis, and dynamic testing.

Reviews, static analysis, and dynamic testing have the same objective of identifying defects.

Option A is the correct answer.

Option B is incorrect because fixing defects is not the objective of reviews, static analysis, and dynamic testing. Their objective is to identify defects so that they can be reported for fixing.

Option C is incorrect because the statement "1 and 2" is not clear. It is not clear what "2" is referring to, and it is unclear how it is related to the objective of identifying defects.

Option D is incorrect because, as mentioned earlier, the objective of reviews, static analysis, and dynamic testing is to identify defects. Therefore, the statement "None" is incorrect.

The Answer is: A

The defect arrival rate curve tracks the rate at which new defects are discovered over time, showing the flow of defects being found rather than cumulative totals or open defects. Option A correctly identifies this as 'newly discovered defects per unit time' - it's a rate metric, not a cumulative count. Option B describes defect backlog, while Option C would be a cumulative defect curve.

Risk analysis fundamentally evaluates two dimensions: likelihood and impact. The probability of a negative event occurring (Option A) must be weighed against the potential loss or damage that would result if it did happen (Option B). This probability-impact matrix forms the basis of all risk assessment frameworks - without knowing both factors, you cannot prioritize risks effectively.

Statement coverage only guarantees that every line of code executes at least once, but this has critical limitations. Option A describes control-flow dependencies: a bug might only appear when taking one branch of a conditional, but your test might only exercise another branch. Option B describes data-flow problems: certain bugs depend on specific input values that trigger edge cases, regardless of code path. Both scenarios mean 100% statement coverage can still miss serious defects.

The test manager bears primary responsibility for test readiness review because this is a management-level gatekeeping function, not a technical execution task. The review evaluates whether testing artifacts are complete, requirements are traceable, entry criteria are met, and the test team is prepared to begin formal testing. While test engineers contribute materials and participate, the test manager conducts and signs off on this review.

When project scale limits testing resources, risk-based analysis becomes the critical prioritization tool (Option A). This approach identifies high-risk areas requiring thorough testing while accepting lower coverage in safer, lower-impact components. Option B (automation tools) addresses execution efficiency but not scope prioritization. Risk analysis provides the strategic framework for allocating limited testing effort where it matters most.

Configuration Management in testing focuses on identification (knowing which software version you're testing - i), version control (managing testware versions - ii), and change tracking (knowing what changed and when - iv). Developing new testware (iii) and analyzing needs (v) are test design and analysis activities, not configuration management functions.

To answer this question, the user needs to know the basic tasks and objectives of test planning.

The correct answer is:

A. Scheduling test analysis and design tasks.

Explanation:

Test planning is a critical phase of the software testing life cycle. It involves defining the approach, objectives, and scope of testing, as well as identifying the necessary resources, tools, and techniques to achieve the desired results.

A major task of test planning is scheduling test analysis and design tasks. This involves determining the testing activities that need to be performed, allocating the necessary resources and time for each activity, and creating a timeline or schedule for completing the tasks. This ensures that the testing process is systematic, organized, and efficient.

Initiating corrective actions, monitoring progress and test coverage, and measuring and analyzing results are important tasks in software testing, but they are not the major tasks of test planning. These tasks are typically performed during the testing execution and evaluation phases.

Therefore, option A is the correct answer.

Functional testing verifies what the system does and can be performed at every test level. Unit tests check individual functions, integration tests verify functional interactions between components, system tests validate end-to-end functionality, and acceptance testing confirms business requirements are met - all are functional in nature.

Reviews identify defects in ANY software work product (requirements, code, test cases, documentation) not just application failures (which are caught by testing). A review looks for problems before execution, whereas testing finds failures during runtime. Option C and D are too narrow - reviews cover more than just spelling or code standards.

Debugging is the process of identifying, locating, and correcting bugs within the source code, which is traditionally and primarily performed by developers who write the code. Testers typically find and report defects, but they do not debug the source code to resolve them.

In software testing, configuration management ensures that all versions of the software under test (i) and the associated testware (test scripts, plans, data) are identified (i), version-controlled (ii), and tracked for changes (iv). Developing (iii) or analyzing the need for new testware (v) are development/analysis activities, not configuration management.

Test planning involves defining the overall test approach and scheduling activities. Scheduling test analysis and design tasks (what to test, how to test) happens during planning. Options B, C, and D (corrective actions, monitoring, measuring) are part of test control/execution, not planning.

Functional testing (testing based on functional requirements) can be performed at ANY test level. At unit level, you test individual functions. At integration level, you test interfaces between modules. At system and acceptance levels, you test end-to-end functionality. Options A, C, and D incorrectly limit where functional testing applies.

Reviews identify defects in ANY software work product (requirements, code, test cases, documentation) not just application failures (which are caught by testing). A review looks for problems before execution, whereas testing finds failures during runtime. Option C and D are too narrow - reviews cover more than just spelling or code standards.

Debugging is the process of locating and fixing defects, which requires access to source code and development tools. Developers write the code and are responsible for fixing it. Testers find and report incidents, but don't typically debug. Analysts define requirements, and incident managers track issues.

The ObjectRepositoryUtil utility in QTP (QuickTest Professional, now UFT) provides programmatic API access to manipulate both Shared Object Repository files (.tsr) used across multiple tests and Local Object Repository files (.mtr) specific to individual tests. This enables automation of repository management tasks from outside the QTP IDE.

The Object Repository Manager in QTP/UFT allows you to open and work with multiple shared object repositories simultaneously. This is useful when your test uses objects from different repositories. Options like 'Two', 'Three', or 'Seven' are arbitrary limits - the tool supports multiple repositories without a fixed upper bound.

The 'Associate Repositories' dialog box is used to manage which shared object repositories are linked to a specific test or action. This is where you add, remove, or change the order of associated repositories. Note the typo in the option - it should be 'dialog' not 'dailog'.