Software Testing: Automation and Performance Testing

Throughput in web application performance refers to the volume of work completed in a given time period, typically measured as transactions or requests per second/minute. Option A directly captures this definition. CPU utilization (Option B) and memory consumption (Option C) are resource utilization metrics. Concurrent users (Option D) is a load metric, not a throughput measure.

Transaction Mix refers to the varying execution frequency of different transaction types in a workload. For example, in an e-commerce site, browse transactions might occur 80% of the time while checkout occurs 15% and account management 5%. Options B, C, and D describe static concepts, not the frequency distribution aspect.

VSTS (Visual Studio Team System) web tests support multiple parameterization sources including databases, XML files, and CSV files. This allows test data to be externalized and varied across test iterations. Since all three sources (DB, XML, CSV) are supported, Option D is the correct comprehensive answer.

VSTS load testing supports both Goal Based testing (where the test runs until a specific performance goal is met) and Step Load testing (where load increases in steps or increments over time). Option C correctly identifies both supported load test types. Option D 'None' is incorrect.

Response time is the time elapsed from sending a request to receiving the complete response. In this scenario, the 30-second delay from clicking login to seeing the homepage is the response time. Wait time (Option A) and Transaction Delay (Option B) are not standard performance testing terms. Transaction wait time (Option D) is not a defined metric.

Planning performance tests requires comprehensive information including workload characteristics (user loads, transaction mix), application details (architecture, technology stack), and monitoring framework setup (what metrics to capture, tools). All three inputs (Options A, B, C) are essential prerequisites, making Option D the correct answer.

The scenario requires determining current capacity to decide between horizontal (adding servers) or vertical (upgrading servers) scaling. Load testing simulates expected user loads to measure current system capacity and identify scaling points. Stress testing (Option B) finds breaking points. Volume testing (Option C) tests with large data volumes. System testing (Option D) is functional, not performance-focused.

Even after performance testing and tuning, systems can encounter performance problems when they grow (increased users, data, or traffic). Tuning is not permanent - it optimizes for current conditions. Option A is incorrect because performance problems can recur. Option B claims it will have problems, which is too definitive. Option D incorrectly limits problems to only application changes.

Performance testing requires tools to accurately measure response times, throughput, and resource utilization under load. Manual testing cannot generate consistent load, capture precise timing metrics, or simulate concurrent users. Automated tools like JMeter, LoadRunner, or VSTS are essential for credible performance testing. Therefore, the answer is False - you cannot properly conduct performance testing without tools.

Extensibility is the feature that allows testing custom controls by creating extensions or add-ins. This enables the automation tool to recognize and interact with non-standard or proprietary controls that the built-in support doesn't handle.

UI Automation (UIA) is the Microsoft accessibility framework specifically designed to interact with Silverlight controls. Silverlight exposes its UI elements through UIA, enabling automation tools to identify and manipulate controls programmatically. MSHTML is used for HTML rendering in IE, DOM is for web document structure, and MAUI is a modern cross-platform framework unrelated to Silverlight.

Object Identification is the most critical feature because scripts cannot run without locating UI elements. Asset reusability lowers maintenance overhead, and error recovery ensures unattended test execution. Graphical verification is the least critical due to its susceptibility to minor UI changes.

Starting automation after at least one manual testing cycle ensures the application is stable enough and critical functional flows are understood. Manual testing first helps identify obvious defects and validates that workflows work as expected, preventing automation scripts from breaking constantly. Automating too early leads to high maintenance costs when the UI changes frequently, while waiting until production misses opportunities for early defect detection.

BVT (Build Verification Tests) and Regression test cases are ideal for automation because they are run frequently and involve stable, repeatable scenarios. BVTs verify core functionality after each build, while regression tests ensure existing features still work after code changes. Both types have predictable outcomes and high execution frequency, maximizing automation ROI. Usability testing involves subjective human judgment about user experience that cannot be automated effectively.

Selenium is a free, open-source automated testing framework specifically designed for web application UI automation. The other options listed (Visual Studio Coded UI Test, QTP/QuickTest Professional, and Rational Functional Tester) are all commercial tools requiring expensive licenses. Selenium's open-source nature makes it widely accessible for teams without budget constraints on testing tools.

Object synchronization in test automation refers to waiting mechanisms that ensure the AUT (Application Under Test) reaches the expected state before the automation script interacts with it. This prevents script failures due to timing issues, such as attempting to click a button before it becomes enabled or visible. Synchronization handles dynamic page loads, AJAX calls, and asynchronous operations that cause delays between script actions and UI responsiveness.

When automation IDs are duplicated across controls, automation tools use property combinations like name, class name, parent hierarchy, or XPath to uniquely identify each control. A single property might not be sufficient, so tools use multiple attributes together to create a unique selector. Modern automation frameworks can handle this common scenario through composite identification strategies rather than failing when IDs are not unique.

Test automation tools identify controls using identification properties stored in a GUI map or object repository, which maps logical names to physical control properties like name, ID, class, or XPath. This abstraction layer separates test scripts from UI property changes, improving maintainability. X-Y coordinates are unreliable because UI elements can move, hidden algorithms would not be useful to testers, and relative positioning is less robust than property-based identification.

MAUI (Microsoft Automation UI) is Microsoft's internal automation tool used within the company for testing purposes. Coded UI Test is a publicly available Microsoft Visual Studio feature, not internal. QTP (QuickTest Professional, now UFT) is a Micro Focus/HP product, not Microsoft. Therefore, only MAUI qualifies as a Microsoft internal tool among the options.

Test automation provides both higher coverage (executing more test cases in less time) and repeatability (running the same tests consistently without human error). Higher coverage is achieved because automated tests can run continuously, including overnight and in parallel. Repeatability ensures tests execute identically each time, eliminating variability inherent in manual testing. Less dependency on manual testers is a consequence, not the advantage itself.