Software Testing Automation Tools and Concepts

Test Procedure Specification describes the detailed steps required to execute test cases. It specifies how to operate the system and exercise test cases to implement the test design. Test Case Specification defines individual test cases, and Test Design Specification defines the overall test approach.

To answer this question, the user needs to know what verification means in the context of software development. Verification is the process of evaluating a system or component to determine whether it meets the specified requirements and satisfies its intended purpose. With that in mind, let's evaluate each option:

A. Helps to check the Quality of the built product: This option is correct. Verification helps to check the quality of the built product by ensuring that the product meets the specified requirements and is fit for its intended purpose.

B. Helps to check that we have built the right product: This option is correct. Verification helps to ensure that we have built the right product by checking that it meets the specified requirements and satisfies its intended purpose.

C. Helps in developing the product: This option is incorrect. Verification is a process that occurs after the product has been developed to ensure that it meets the specified requirements and is fit for its intended purpose. It does not help in developing the product.

D. Monitoring tool wastage and obsoleteness: This option is incorrect. Verification is not concerned with monitoring tool wastage and obsoleteness.

Therefore, the correct answer is:

The Answer is: A and B.

EULA stands for End User License Agreement. It is a legal contract between the software creator and the user that specifies the terms under which the software may be used.

Beta releases are early builds distributed to select customers and marketing for demonstration purposes. Alpha releases are even earlier and typically internal-only. A Build is a generic compiled version, and Test release document is not a standard release phase.

The amount of testing required depends on multiple factors including industry risk, contractual obligations, and special requirements. There is no single answer - it is a risk-based decision.

With two independent conditions in nested if statements, we need 2 test cases: (1) Condition 1 true, (2) Condition 1 false. When Condition 1 is false, we never reach Condition 2 due to the else branch. When Condition 1 is true, we always execute statement 3 regardless of Condition 2. Thus only 2 paths are possible.

Selenium is a well-known open-source web application testing framework. AutoHotkey is open-source automation scripting software. Maveryx is an open-source test automation tool for Java/GUI applications. Eggplant is a commercial, proprietary testing tool (not open-source). Therefore options A, B, and C are correct while option D is incorrect.

Selenium was created by Jason Huggins in 2004 at ThoughtWorks. He developed it to automate testing of web applications to avoid repetitive manual testing. Bjarne Stroustrup created C++, while David Hopes and Thomson Davis are not associated with Selenium's development.

QTP (QuickTest Professional, now UFT - Unified Functional Testing) supports both keyword-driven and data-driven testing approaches. Keyword-driven testing uses keywords to represent actions, while data-driven testing allows running the same test with multiple data sets. This dual support makes QTP versatile for different testing methodologies.

QTP scripts are browser-specific and must be recorded or modified for each different browser. The same script cannot run across all browsers without adjustments because each browser renders web elements differently and may require different object identification properties. Cross-browser compatibility testing requires separate scripts or significant modifications.

AutoHotkey is a powerful automation scripting language that can indeed launch programs, send keystrokes and mouse clicks, work with variables for data storage and manipulation, run loops for repetitive tasks, and manipulate windows. All these capabilities are core features that make AutoHotkey useful for task automation and creating custom macros.

QTP (QuickTest Professional) does support testing of Windows Mobile applications through its add-in architecture. QTP provided specific add-ins for different technologies including mobile platforms. However, this support may have evolved or changed as mobile testing frameworks have modernized and Windows Mobile has been phased out.

Ranorex is indeed a comprehensive test automation framework that supports testing various types of applications including desktop, web, and mobile applications. It has specific support for modern Web 2.0 applications with rich internet applications, AJAX, and dynamic content. Ranorex provides a complete IDE for test automation with record and playback capabilities.

HP WinRunner was originally developed by Mercury Interactive, which was later acquired by Hewlett-Packard in 2006. Mercury Interactive was a software testing company that created several testing tools. WinRunner was one of their flagship automated testing products before HP acquired the company and rebranded the products.

Selenium, CubicTest, and Tellurium are all open source testing automation tools. TestPartner, however, is a commercial testing tool originally developed by Compuware and now owned by Micro Focus. It requires a license and is not available as open source software, making it the correct answer for 'not an open source tool'.