Software Testing Tools and Methodologies

SilkTest is a test automation tool originally developed by Segue Software, which was acquired by Borland in 2006. HP owns QuickTest Professional (now UFT), Mercury Interactive was acquired by HP, and IBM owns the Rational suite of testing tools.

iMacros is a free Firefox add-on for recording and automating web interactions. While other automation tools exist, the question specifically asks for free Firefox add-ons, and iMacros fits this description. 'Macros' alone is not specific enough and 'both' is incorrect.

WATIR stands for Web Application Testing in Ruby. It is an open-source family of Ruby libraries for automating web browsers. The key distinction is 'Web' not 'Windows' and 'Application Testing' not 'Automation Testing'.

Fiddler is a widely used HTTP debugging proxy that captures and logs all traffic between a computer and the internet. Httpwatch is a browser plug-in rather than a standalone proxy, and the others are not standard tools for this specific purpose.

BVT (Build Verification Testing) is a type of regression testing that verifies core functionality after a new build. It ensures the application is stable enough for further testing. It's not performance, volume, or security testing.

BVT is typically performed by developers as part of the build process, but testers can also run BVT suites. This is a standard practice in software development where smoke tests or sanity tests are executed after deployment.

BVT is not manual - it's typically automated to run quickly after each build. Manual BVT would defeat the purpose of rapid build verification. Automation tools execute BVT scripts efficiently.

BVT (Build Verification Testing) typically consists of Build Validation, which ensures the build is stable enough for testing, and Build Acceptance, which confirms the build meets the basic requirements to enter the test cycle. Other options use redundant or incorrect terminology.

HP Quality Center (now Micro Focus ALM) is a web-based test management tool used for managing testing processes, not test automation, test case design, or load testing. Option B is correct.

Quality Center 9.2 (now HP ALM) was designed for Internet Explorer as the primary supported web client. During that era, enterprise applications heavily relied on IE-specific technologies like ActiveX. Modern browsers like Firefox and Safari lacked necessary plugin support. Netscape was already obsolete by QC 9.2's release. IE's dominance in enterprise environments made it the practical choice.

Quality Center (HP ALM) has 5 main modules: Requirements for defining requirements, Test Plan for designing test cases, Test Lab for executing tests, Defects for tracking bugs, and Dashboard for reporting and analysis. This modular structure provides comprehensive test management capabilities.

The Requirements module is the designated place in Quality Center where you create and link tests to requirements, ensuring each requirement has test coverage. This establishes traceability from requirements through test execution.

In Quality Center, traceability is bidirectional: Requirements show Test coverage (linked tests), and Test Plan shows Requirement coverage (linked requirements). This full traceability matrix ensures every requirement is tested and every test can be traced back to requirements.

The Test Lab module is specifically designed for test execution, where you create test sets, schedule runs, and execute test cases. Test Plan is for designing tests, not running them.

In Quality Center's Test Plan module, you create the test plan tree by manually defining folders to organize tests and then creating individual tests within those folders. This hierarchical structure organizes your test repository.

Requirement traceability is the process of documenting the relationships between requirements, as well as between requirements and other artifacts like tests or design documents, to track dependencies.

The 'Select Test' button in Test Lab opens a dialog where you can browse and select tests from the Test Plan tree to add into your test sets. This is how tests move from planning to execution.

Quality Center 9.2 supports Microsoft SQL Server and Oracle as its backend database options for enterprise deployment. These are the two database platforms certified for QC 9.2; Access, Sybase, and Paradox are not supported.

Quality Center 9.2 supports Microsoft SQL Server and Oracle as its backend database options for enterprise deployment. These are the two database platforms certified for QC 9.2; Access, Sybase, and Paradox are not supported.

Quality Center Dashboard provides executive-level visualization and reporting, offering high-level metrics, graphs, and status views of the entire testing process for management oversight.