Software Testing and QTP Automation

SilkTest has three default testplan attributes: Category, Severity, and Priority. These are built-in attributes that come with every new test plan and are used to organize and classify test cases.

In 4Test (SilkTest's language), to convert a string to an integer, you declare an INTEGER variable and use the Val() function. The syntax 'INTEGER iTemp = Val("100")' correctly declares the variable and converts the string "100" to its numeric value. Options A, B, and C have incorrect syntax for 4Test.

QuickTest Professional (QTP), now known as Unified Functional Testing (UFT), uses VBScript as its scripting language. VBScript is a lightweight, interpreted scripting language based on Visual Basic that allows testers to write automated test scripts with programming constructs like loops, conditions, and functions.

QTP has three recording modes: Normal recording (default), Analog recording (for exact mouse movements and keystrokes), and Low-level recording (for recording at object level even when standard recording fails). Option B (2 modes) is incorrect as all three modes are available.

In QTP, running multiple tests together is called Batch Test. This feature allows you to execute a series of tests in sequence without manual intervention. Option A (Group test) and B (Batch run) are not the standard terminology used in QTP documentation.

QTP handles exceptions using Recovery Scenarios, which allow you to define trigger events, recovery operations, and post-recovery test run options. This is QTP's built-in mechanism for handling unexpected events, errors, or application crashes during test execution. Option C (Exception handler) is a general programming term but not QTP-specific.

The waitproperty method is used for synchronization in QTP. It pauses test execution until a specified object property achieves a certain value or times out. This is the preferred synchronization method over static waits like wait() or sleep() because it waits dynamically based on application state rather than fixed time intervals.

Code-driven test automation is a key feature of Agile software development. Agile emphasizes continuous testing and test automation as integral parts of the development process, with code-driven tests supporting continuous integration, regression testing, and rapid feedback cycles. RAD (Rapid Application Development) and PAD are different methodologies not primarily characterized by code-driven automation.

Data-driven testing framework involves creating test scripts that operate on different sets of input data and expected results, stored externally. The same test script can be executed multiple times with different data combinations, maximizing test coverage with minimal script maintenance. Code-driven testing focuses on script logic, while key-driven testing uses data tables for step-by-step execution.

Test script modularity framework requires creating small, independent scripts representing modules, sections, and functions of the application. Each script encapsulates a specific component or functionality, promoting reusability and maintainability. These modular scripts can be combined to form larger test scenarios, reducing redundancy and making updates easier when application changes occur.

Boolean solvers can solve sets of constraints using numerical analysis techniques like Gaussian elimination, which systematically eliminates variables to solve systems of linear equations or constraints. This method is fundamental in constraint satisfaction problems. Options A, B, and D describe binary/boolean concepts but are not examples of constraint-solving techniques.

Markov chains in Model-Based Testing are best understood as Finite State Machines weighted by probabilities on transitions. Each state represents a test condition, and transitions represent possible paths with associated probabilities. This allows statistical generation of test cases and coverage assessment based on transition likelihoods. State transition diagrams are unweighted, while entity-relationship and data flow diagrams represent different modeling concepts.

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.

Output parameter is correct because it specifically captures data from one screen/action to be used as input for the next. Output parameters store values generated during test execution that need to be passed to subsequent steps. Parameterization is a broader concept for data-driven testing, while input parameter receives data rather than capturing it.

All the above is correct because QTP (QuickTest Professional) supports three main testing approaches: Keyword-driven (using keywords to represent test steps), Data-driven (separating test logic from test data), and Hybrid (combining both keyword and data-driven approaches). Each approach has its use cases in test automation.

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.

HP is correct as QTP (QuickTest Professional) was originally developed by Mercury Interactive, which was acquired by HP in 2006. QTP became an HP product (later called UFT - Unified Functional Testing). The option "Both 1 & 2" would also be historically accurate, but HP is the most direct answer as the current owner at the time of QTP's prominence.

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.