Software Testing and Quality Control

Parameterization is the correct answer because it is specifically designed to execute the same test with multiple sets of data. This technique allows you to separate test logic from test data, running the test script iteratively with different data values. Parameter is a general concept, Keyword refers to keyword-driven testing, and Expert is not a standard testing approach.

All the above is correct because different methods are used in different contexts to retrieve text values. GetROProperty retrieves runtime object properties including text, GetVisibleText captures visible text on screen, and GetText is used for retrieving text from specific objects. The appropriate method depends on the testing scenario.

The SQL Performance Monitor is a tool specifically designed to analyze and monitor database operations performance on DB2 for i5/OS systems. It helps database administrators track query execution, identify performance bottlenecks, and optimize database operations. The other options describe different DB2 tools like the Health Monitor (A), Visual Explain (B), and Task Center (C).

Test conditions are derived from specifications including requirements documents, design specifications, and functional specifications. These conditions identify what needs to be tested, serving as the foundation for creating detailed test cases. Test cases are then developed FROM test conditions, making B incorrect, while test data supports test case execution rather than deriving conditions.

To solve this question, the user needs to understand the concept of software testing and the different types of testing.

The given description refers to the process of testing a modified program to ensure that any changes made have not introduced new defects or uncovered defects that were not present before. This is known as regression testing.

Option A, Re Testing, refers to the process of testing a program again after defects have been fixed.

Option B, Confirmation Testing, is a type of testing that ensures that defects that were previously identified and fixed have not reoccurred.

Option C, as mentioned earlier, is the correct answer. Regression testing is performed after modifications to a software component to ensure that the changes have not introduced new defects.

Option D, Negative Testing, is a type of testing that checks the behavior of a program when it is given invalid inputs or unexpected user behavior.

Therefore, the correct answer is:

The Answer is: C, Regression Testing

User Acceptance Test (UAT) cases are derived from requirement specifications to validate that the delivered system meets end-user requirements and business needs. Integration test cases focus on interfaces between components, unit test cases verify individual functions in isolation, and program specifications are technical implementation documents rather than test inputs.

Test Analysis and Design includes evaluating testability of requirements and systems, identifying test conditions, and designing test cases. Test Planning focuses on strategy, resources, and schedule. Test Implementation involves preparing test specifications and setting up test environments. Evaluating exit criteria happens after test execution as part of test closure.

Contributor is a standard SharePoint permission level that allows users to add, edit, and delete items in lists and document libraries. Developer, Creator, and Tester are not standard SharePoint security/permission levels. The standard levels include Full Control, Design, Edit, Contribute, Read, etc.

Exhaustive testing is indeed impossible for any non-trivial software system. The number of possible input combinations, paths, and states is effectively infinite. Testing must therefore be risk-based and prioritized rather than exhaustive. This is a fundamental principle in software testing.

Smoke testing is the correct approach - it quickly verifies that the most critical functions of a build work before full deployment. Static testing examines code without execution, while dynamic testing involves running the code.

All three components are essential to scorecard testing: verifying TAR (Transaction/Account Rating) rules, checking Scorecard Attributes for proper data mapping, and validating Tier Cutoffs ensure correct segmentation.

Smoke testing is the standard practice for testing a candidate build before deployment. A smoke test verifies that the most critical functions work - it's a quick sanity check to ensure the build isn't completely broken. Static testing analyzes code without running it, dynamic testing involves detailed runtime analysis, but smoke tests are the standard for deployment validation.

Agent testing is always performed in TAC (likely 'Test Agent Console' or similar) environment. DEV is for developer testing, and TIN is for IT/system testing. TAC is specifically designed for agent-level testing with the appropriate interface and permissions that agents would use. This separation ensures agents don't accidentally access development tools or system-level test regions.

According to standard testing definitions (like ISTQB), a test condition is an item or event of a component or system that can be verified by one or more test cases. Option 1 defines a test case, and option 2 defines a test procedure or test script.