Software Testing and Quality Control

Quick Test Professional (QTP), now known as Unified Functional Testing (UFT), is designed specifically for functional and regression testing of applications. Load Runner is for performance testing, Selenium primarily for web functional automation, and SOA tool is too vague to be the standard functional regression tool.

Load testing is a non-functional testing type because it measures system performance, response times, and stability under load rather than validating functional behavior. System testing, unit testing, and sanity testing all verify that the software functions correctly according to requirements.

Stress testing involves evaluating a system's robustness under extreme conditions, such as high load with restricted resources, to observe how it fails. Regular load testing measures performance under normal loads.

Regression testing is designed to verify that recent code changes or bugfixes have not adversely affected existing, unchanged features of the software application, preventing the recurrence of old bugs.

Security testing is the correct answer because it explicitly validates authentication mechanisms, session management, cookie handling, and access controls. Cookie and session management are critical security features that must be tested for vulnerabilities like session hijacking, cookie tampering, and unauthorized access.

Unit testing in MVC allows testing all aspects of controller actions: the returned view, the ViewData dictionary, and the ActionResult type itself. This comprehensive testability is a key advantage of the MVC architecture.

Return codes can be tested before execution of a job step through the RC parameter. COND (C) is used for conditional execution based on return codes, but RC is specifically for testing return codes themselves. CODE (B) and RETURNCD (D) are not correct parameters.

In Android, test applications can run in the same process as the application under test using the android:targetProcess attribute or by not specifying a separate process. This is useful for faster testing and direct access to application components, though running in a separate process provides better isolation.

Eclipse with ADT was the primary IDE for Android development before Android Studio, providing integrated testing capabilities. The Android Debug Bridge (adb) tool enables command-line testing, debugging, and device interaction. Ant build system includes targets for running tests and building test APKs. These are all valid approaches to Android testing.

Android test applications can verify functional correctness (business logic), Activity lifecycle behavior (onCreate, onResume, etc.), database CRUD operations, and UI behavior across different screen sizes and resolutions using instrumentation and test frameworks like Espresso or UI Automator. All listed areas are valid test targets.

Android test applications extend the standard Android Application class and include a test runner in their manifest. They have access to Android APIs, can declare their own components, and are APKs like any other Android app, with the addition of test-specific manifest entries and dependencies on the app under test.

In LoadRunner, a Scenario file defines the overall execution details of a load test, including the specific Vusers, load generators, and test goals. In contrast, Scripts contain the actions recorded for Vusers, and the Analysis tool is used to analyze results post-run.

When load testing checkout and checkin actions, they must be performed as a sequence: checkout followed by checkin. Performing only one action would lead to dirty states or resource locks, and performing checkin first is impossible if the resource is not already checked out.

Performance testing evaluates system characteristics like speed, scalability, and stability, which are non-functional aspects of software. Unit, regression, and black box testing are functional testing types because they verify if the software functions correctly according to its business logic and specification requirements.

Non-functional testing evaluates software quality attributes rather than specific behaviors. Performance testing checks how well the system performs under various conditions, which is a non-functional requirement. Unit testing, black box testing, and regression testing can test functional or non-functional aspects.