Software Testing and Quality Control

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 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.

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.

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.

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.

Out-of-synch is a condition identified through the audit process in ChangeMan, indicating inconsistency with development procedures or other code problems. It occurs when components don't match their expected state. Divide by zero and SOC7 are runtime abend conditions, while If condition is a programming construct.