Software Testing Fundamentals and Frameworks

A failure is the departure of the system from its specified behavior - it's what the user observes when the software doesn't work as expected. An error is a human mistake that causes a defect (bug) in the code, and when that defect is executed, it causes a failure. Option C describes a defect, option D describes an error, and option A is incomplete.

The statement appears to reference browser-specific syntax or object models. The correct answer is False, suggesting that .Object IS recognized by Firefox.

Firefox can differentiate between window objects and web objects. The DOM model allows distinguishing between the browser window and document content.

This appears to reference browser-specific syntax differences. The correct answer is False, indicating that empty string handling differs between IE and Firefox.

Firefox and IE handle HTTP requests differently due to different rendering engines and browser architectures. The statement is False.

The syntax ".Object" with a leading dot is invalid JavaScript and will not be recognized by any browser including Firefox. Object references must start with the window object or a valid identifier.

Firefox correctly differentiates between the window object and web page objects in the DOM hierarchy. It maintains proper object scope and distinguishes between browser-native and document objects.

In Internet Explorer, you can use an empty string "" with the Set method, but Firefox requires a space " " instead. This is a known cross-browser compatibility difference.

Firefox and Internet Explorer handle HTTP requests differently, including headers, caching behavior, and object models. The requests taken by each browser are not the same.

Functional testing focuses on validating that the system behaves according to requirements by examining inputs and outputs without regard to internal implementation. It tests 'what' the system does rather than 'how' it does it internally. System testing is broader (tests entire system), Acceptance testing validates against user/business requirements, and White box testing specifically DOES look at internal code/logic - making it the opposite of what the question describes.

Functional testing focuses on validating that the system behaves according to requirements by examining inputs and outputs without regard to internal implementation. It tests 'what' the system does rather than 'how' it does it internally. System testing is broader (tests entire system), Acceptance testing validates against user/business requirements, and White box testing specifically DOES look at internal code/logic - making it the opposite of what the question describes. Note: This is a duplicate of question 134086.

Performance testing is the umbrella term that encompasses stress testing and load testing. Load testing checks system behavior under expected load, stress testing pushes beyond expected limits, and performance testing evaluates overall system responsiveness, stability, and scalability under various conditions. The other options are unrelated: Recovery testing checks system recovery after failures, Compatibility testing validates interoperability, and Comparison testing compares different versions or systems.

Sanity testing is a quick, cursory testing performed to determine if a new software version is stable enough to warrant further major testing efforts. It's a subset of regression testing focused on core functionality. If sanity testing fails (major bugs in critical features), the build is rejected without wasting time on comprehensive testing. Regression testing is broader (checks all functionality), Load testing checks performance under load, and Install/Uninstall testing validates installation processes.

Smoke testing (also called build verification testing) is performed to check if the application is stable enough for further major testing and is working properly without failing in critical areas. It's a preliminary testing to determine the basic 'smoke' doesn't come out of the application when run - indicating it's stable enough for deeper testing. Sanity testing is similar but narrower (tests specific fixes), Load testing checks performance, and Usability testing evaluates user experience.

Adhoc testing is informal testing done without formal planning or documentation. System integration testing is structured, stress testing checks system limits, and ADA testing relates to the Americans with Disabilities Act - not relevant.

Black box testing primarily uses two techniques: equivalence partitioning and boundary value analysis. These are the fundamental black box approaches for test case design.

Ad-hoc frameworks have three key characteristics: (A) Some data in datasheet but not truly data-driven, (B) Test steps embedded in Action scripts (high maintenance, low reuse), and (C) Reactive scripting for single issues. These describe poorly structured automation. Option D (None) is incorrect because A, B, and C all accurately describe ad-hoc framework traits.

Test Script Modularity framework emphasizes creating small, independent, reusable script modules (B) which improves maintainability (A) and uses abstraction layers to hide components (D). It does NOT heavily depend on datasheets for each execution - that describes a data-driven framework.