Software Testing and QA Fundamentals

Re-testing (or confirmation testing) specifically reruns failed test cases to verify that a previously identified defect has been successfully fixed. In contrast, regression testing is performed on unchanged parts of the software to ensure that recent modifications have not introduced unexpected side effects or new bugs.

Testing is fundamentally about finding defects in software, not about proving that it works or is defect-free. Option D correctly states that testing executes software to find defects, which is the standard definition in software engineering. Options A, B, and C are incorrect because they suggest testing proves perfection or functionality, which is impossible to guarantee.

Test script names in automated testing frameworks typically allow alphanumeric characters and underscores. Option A is correct as it specifies the valid characters: alphabets, numbers, and underscores. Special characters like *, (), # are generally not allowed in script names.

Recovery Scenario files in QTP (QuickTest Professional) use the .qrs file extension. QTP is a functional testing automation tool, and Recovery Scenarios are used to handle unexpected errors or events during test execution. The .qrs extension specifically identifies these recovery configuration files. The other extensions (.tsr, .prs, .trs) are not associated with QTP Recovery Scenarios.

In QTP (QuickTest Professional) scripting, function names must follow specific naming conventions. The function name must start with 'func' followed by the actual name. 'funcOpenWindow()' follows this convention correctly. The other options are invalid: 'functionOpenWindow()' uses the full word 'function', 'funOpenWindow123()' is an incorrect abbreviation, and 'OpenWindow()' lacks the required prefix. These naming rules help distinguish user-defined functions from built-in functions and keywords.

A Project Completion Report (PCR) is a formal document that signals the official closure of a project. Consequently, it is signed off at the End of the Project to confirm all deliverables are met. Signing it at the beginning or during development/testing stages would be premature and incorrect.

AMRO (Account Management and Reconciliation Operations) database is the repository where BANs (Billing Account Numbers) required for testing are identified and stored based on project criteria. V21 DB and Reference DB serve different purposes in the testing infrastructure.

The QA environment has 5 integrated environments available for testing at different stages and configurations. These multiple environments allow for parallel testing activities and isolation of different test scenarios.

System Functional Testing begins during the Task phase in test execution, after Entry criteria are met and before Exit criteria evaluation. The Validate phase focuses on validation rather than functional testing execution.

The correct QA testing sequence is System Integration Testing (SIT) → QA → Performance Testing → User Acceptance Testing (UAT) → Operational Readiness. This order ensures systems are integrated before functional QA, performance is validated after functional correctness, and user acceptance precedes operational readiness.

AWE (Application Workbench for Enterprise) is the repository used for managing and reporting projects. AMG, SMS, and SS are different systems with other purposes in the enterprise architecture.

When a developer fixes a Pest (defect), the status is assigned as Resolved to indicate the fix is complete and ready for verification. The Pest is only Closed after QA verification confirms the fix works. Reassigned and On Hold are different workflow states.

Severity (impact on system) and Priority (business urgency) should match each other for proper defect triage - high severity defects should be high priority. This matching ensures resources are allocated appropriately to critical issues.

Pests raised for invalid or unsubstantiated defects are marked as Deferred Pests in this system's terminology. This differs from Invalidated Pests which may indicate a different status. On Hold and Resolved are active states for valid defects.

In testing terminology, pests (defects or issues) are prioritized based on both blocked AND failed test cases. Blocked cases indicate testing cannot proceed, while failed cases indicate actual defects. Both metrics together help determine which issues need immediate attention.

Quality Assurance covers both new and existing applications - it's about ensuring quality across all software, not just new developments or just maintenance. QA activities include testing both newly implemented features and verifying existing functionalities continue to work correctly.

Test plan creation happens BEFORE data planning. The test plan defines the scope, approach, resources, and schedule for testing. Only after understanding what needs to be tested can you plan the data requirements for those tests. Data planning depends on the test plan.

ETVX is a process model standing for Entry, Task, Validation/Verify, and Exit. It defines a structured approach where Entry criteria must be met to begin work, the Task is performed, Validation verifies correctness, and Exit criteria must be met to complete the process.

Under the ETVX (Entry, Task, Verification, Exit) process model, the actual action of reviewing the Functional Requirements Document (FRD) for completeness and correctness is classified as a Task. Entry criteria define prerequisites, Validation/Verification tests the output quality, and Exit criteria determine completion, making Task the correct phase.