Software Testing and Quality Control

In Pega PRPC class hierarchy, work objects can be instantiated from classes derived from Work- base class, as well as from top-level classes. The class hierarchy supports flexible instantiation patterns while maintaining proper inheritance. Top-level classes provide another entry point for creating work objects outside the standard Work- hierarchy.

Security must be integrated throughout all phases: design, development, and testing. Focusing on only one phase leaves vulnerabilities. Security by design is most effective when applied continuously.

White-box testing (also called glass-box or clear-box testing) involves full knowledge of the application's internal structure, code, and logic, allowing testers to examine paths, conditions, and data flow. Black-box testing treats the application as an opaque system, testing only inputs and expected outputs without seeing internal code. White-box is typically done by developers, while black-box simulates an external attacker or user perspective.

White-box testing involves analyzing the actual source code, byte code, or binary of an application to identify security vulnerabilities, coding errors, and suspicious patterns. Using regular expressions (regex) to scan code for known vulnerability patterns, dangerous function calls, or tainted data flow is a classic white-box static analysis technique. Black-box testing only tests the running application without code access, while grey-box combines both approaches.

Software testing is often legally mandated or required by contracts and specific standards (e.g., safety-critical system regulations). Thus, the statement is correct, making True the right option and False incorrect since testing is frequently obligatory for compliance.

Quality assurance encompasses multiple activities including maintaining development standards, providing training, and conducting defect analysis. All these elements work together to ensure software quality throughout the development lifecycle.

Deciding when to stop testing must balance risk factors (including technical, safety, and business aspects) alongside project constraints (such as time and budget). Since both elements are essential to the decision, choosing only risk or only constraints is incomplete, making 'both 1 and 2' correct.

Debugging is the process of identifying and fixing defects, which is primarily done by developers who write the code. Testing is the process of evaluating software to find defects, which is primarily done by testers who verify the system from a user perspective. This separation of concerns helps maintain objectivity in testing.

The absence-of-errors fallacy is a fundamental testing principle stating that finding and fixing defects does not guarantee a usable system. A system can be defect-free but still fail to meet user needs or business objectives. Testing is context-dependent, exhaustive testing is impossible, and early testing is actually recommended.

Test analysis and design is the phase where testability is evaluated. During this phase, testers examine the test basis (requirements, specifications) and test objects to determine if they can be effectively tested. This includes checking if the requirements are clear, measurable, and testable.

Test closure activities include checking planned deliverables, archiving testware, and handing over to maintenance. Writing a test summary report is actually part of evaluating exit criteria and reporting, not a test closure activity. The test summary report is created earlier when deciding if testing is complete.

Good relationships between testers and developers depend on professional, objective communication. Writing factual incident reports helps developers understand and fix issues without feeling personally attacked. Understanding managers, identifying workarounds, and promoting quality are all valuable but secondary to clear, objective reporting.

Testing is split into distinct stages primarily because each stage serves a different purpose - unit testing checks individual components, integration testing checks interfaces, system testing checks the whole system, etc. This separation ensures comprehensive coverage.

Regression testing involves re-running many existing tests repeatedly after each code change. Test tools automate this efficiently, saving significant time and effort compared to manual execution. Other testing types like UAT, system testing, and integration testing often require more human judgment and exploratory approaches that benefit less from pure automation.