Software Testing and Quality Control

Automation is primarily adopted to reduce testing time (automated tests run much faster than manual testing) and reduce cost (less manual effort required over time, especially for regression testing). Option C 'All of the above' correctly captures both these primary benefits. Option A and B individually are both valid reasons to automate. Option D is not a reason to automate - having a budget is an enabler, not a motivation. Option C is correct.

Stress testing pushes a system beyond its specified limits to find breaking points. Since the requirement states 'up to 10 MB' but we're testing with 100 MB (10x the documented limit), this is stress testing - we're intentionally exceeding normal capacity to observe failure behavior. Load testing tests expected load (within specifications). Functional testing verifies features work as specified. Regression testing checks that changes don't break existing functionality. Option B is correct.

Negative testing involves testing beyond the specified valid boundaries to verify the system properly handles invalid input. Testing with 6 characters when the requirement states maximum 5 characters is testing the failure condition - the system should reject this input. Load testing and stress testing are performance testing types, while regression testing checks for unintended changes after modifications.

The two primary methods of software testing execution are manual testing (where test cases are run manually by a human) and automation testing (where scripts and tools execute the tests). Other options list specific testing types rather than general execution methods.

One of the fundamental principles of software testing is to identify and resolve defects as early as possible in the software development life cycle (SDLC) to reduce the cost and effort of fixing them later.

Testing serves multiple purposes: it finds bugs in the software, provides confidence and information about system quality to stakeholders, and helps prevent defects by identifying issues early. 'All of the above' correctly captures that testing is not just about finding bugs but is a comprehensive quality assurance activity.

A Test Plan is a comprehensive document that details the scope, objective, target market, resources, test environments, features to be tested, test methodologies, tools, and schedule for a testing project, making all options correct.

Load testing evaluates system performance under expected load conditions. Testing the printer with exactly 100 pages in 30 seconds matches the requirement specification, making this load testing - verifying the system meets its stated performance criteria under normal load. Stress testing would exceed this limit to find breaking points.

Error guessing is a black box testing technique where testers use their experience and intuition to make educated guesses about where defects might exist. Unlike formal methods such as equivalence partitioning or boundary value analysis, error guessing relies on the tester's judgment to identify potential error conditions based on common mistakes.

Effective software testing requires curiosity to explore the system thoroughly, a critical eye to identify potential issues and edge cases, and good communication skills to document and report findings clearly. 'All of the above' correctly identifies that successful testing demands all these qualities combined.

Automation testing requires programming knowledge to write and maintain test scripts. Any tester with coding understanding can perform automation testing, distinguishing it from manual testing which doesn't require coding skills. Test leads may or may not do automation - it's a technical skill, not a role-specific one.

Regression testing involves re-running previously executed tests to verify that recent code changes have not adversely affected existing functionality. Re-applying tests from old builds to new builds is the classic definition of regression testing - ensuring nothing that worked before has broken.

A test case is a comprehensive specification that includes what to test, the inputs to be used, expected results, and the conditions and constraints under which testing occurs. 'All of the above' correctly identifies that test cases encompass all these elements to provide complete guidance for test execution.

Stress testing evaluates system behavior under extreme load conditions, often beyond expected capacity. Flooding the system with transactions to test peak performance is stress testing - it pushes the system to its limits to identify breaking points and ensure it handles overload conditions gracefully.

Functional testing evaluates software based on functional requirements - what the system should do from a user perspective. It verifies that each feature of the software operates as specified in the requirements document, making 'Functional testing' the correct answer.