Software Testing and Quality Control

Negative testing validates how the system handles error conditions, such as missing files, format errors, or oversized inputs. Ensuring the database table is accessible to the user is a baseline requirement for normal operations, making it a positive test scenario rather than a negative one.

Batch testing requires critical analytical skills to identify edge cases, basic OS/SQL command knowledge to inspect files and database tables, and a mindset critical of developers' work. Being an automation expert or having specialized QC knowledge are helpful but not essential for basic batch analysis.

Regression testing is performed specifically to verify that recent code changes or updates have not adversely affected existing features. Unit testing checks individual components, whitebox testing is a testing methodology based on code structure, and recursive testing is not a standard term.

AdHoc testing is informal, unstructured testing without documentation, which is a core characteristic of exploratory testing. Unit testing is structured and code-focused, regression testing verifies existing functionality, and performance testing measures system responsiveness.

A Test Bed is the configured test environment including hardware, software, network settings, and data needed to execute tests. Checkpoint and Code Walkthrough are testing techniques, while Checklist is a testing aid.

Stress/Load Testing specifically validates system capacity and performance under expected or peak user/data volumes. Functional Testing checks features work correctly, Recovery Testing ensures backup/restore procedures, and Integration Testing verifies component interactions - none focus on volume handling.

Integration testing strategies include Big Bang (integrating all modules at once), Bottom-Up (testing lower-level modules first), and Top-Down (testing higher-level modules first). Therefore, all are valid types.

FTT stands for Features to Test: a testing document listing the features that need to be tested. It is not about functions, fundamentals, or test execution.

ST04 is designated as the system testing environment in the project's environment naming convention. System testing is where the complete integrated application is tested to verify it meets requirements and works as expected in an environment simulating production.

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.

Peer-to-peer relationship in UML is a type of association where two classes interact as equals, neither containing the other. Unlike aggregation (whole-part) or composition (strong ownership), peer-to-peer represents a collaborative relationship where both classes have comparable status.

The General: Log category in LoadRunner's run-time settings allows developers to configure logging behavior, including the option to send messages only when an error occurs. Meanwhile, Run Logic defines the execution flow, and Miscellaneous governs error handling and threads.