Software Testing & QA Exam Paper 2023
Uploaded by
voodbinodSoftware Testing & QA Exam Paper 2023
Uploaded by
voodbinodCommon questions
Powered by AIIntegrating security testing is crucial for preemptively identifying vulnerabilities, safeguarding data, and ensuring compliance with regulatory standards. However, it is challenging due to its need for specialized tools and skills, potential increase in development duration and costs, and often resistance from development teams prioritizing functional testing. Effective integration requires a balance of resources, clear policy frameworks, and an organizational culture emphasizing security as a priority from the onset .
Selecting an inappropriate review technique can lead to insufficient coverage or oversight of defects. For instance, informal reviews may miss critical technical errors, leading to subpar quality, while overly rigorous techniques like inspections can unnecessarily extend timelines and drain resources. This misalignment affects risk detection efficiency, impacts stakeholder trust due to increased production of defective software, and ultimately heightens maintenance costs and project failure risk .
Alpha testing is conducted at the developer's site by internal teams and focuses on identifying bugs before the software is made publicly available, emphasizing the functionality and stability of the application. Beta testing, in contrast, occurs at the user's site and involves real-world exposure to gather feedback from end users, evaluating user satisfaction and uncover potential defects in diverse environments prior to final release .
Boundary value analysis is a part of black box testing. It focuses on testing the boundaries between partitions. This approach does not require internal knowledge of the software and primarily involves input and output verification to ensure correct behavior across boundary conditions, which contrasts with white box testing that emphasizes examining the program's structural components like code and algorithms .
Designing a test case for an ATM should consider transaction types (e.g., withdrawal, deposit), user authentication mechanisms, error handling for card, PIN, and network failures, variation in transaction limits, different card types, interface responses, and security checks to simulate real user interactions. Environment setup should replicate various operational contexts to validate performance, security, and usability under diverse conditions .
Identifying defects earlier in the SDLC is more cost-effective because corrections made during the initial stages (like requirement analysis or design) require addressing abstract elements such as models and documents, which incur lower costs compared to rectifying implemented code. Late detection may involve reworking extensive code portions, regression testing, and redistributing builds, leading to increased resource and labor costs .
Automated testing boosts efficiency by expediting repetitive tasks, enhancing coverage through consistent test execution, and quickly identifying regressions in functionality. However, its limitations include upfront costs in development and maintenance of test scripts, diminished effectiveness in testing complete user interfaces or nuanced user interactions, and reliance on the accuracy of initially recorded tests, making it less suitable for ever-changing software requirements without frequent updates .
SQA is integral to the SDLC as it embeds quality checks and procedures across phases—from requirements validation, design verification, coding standards, to testing and maintenance. Each SDLC phase includes SQA activities to ensure that outcomes exceed quality thresholds and conform to set standards. The alignment of SQA with SDLC ensures continuous quality improvement and risk mitigation throughout the software's lifecycle, fostering reliable and effective software products .
The RAD model accelerates software development through its distinct phases, including requirements planning, user design, construction, and cutover. Each phase is designed for quick iterations: requirements are gathered swiftly, user design incorporates rapid prototyping with direct user feedback, construction emphasizes modular and simultaneous development, and cutover focuses on the transition to production with minimal delays. This efficiency in dealing with each phase ensures quicker adaptation and delivery of software .
The waterfall model structures software development in sequential phases, each dependent on the delivery of the previous phase, creating a clear project scope and predictable timeline. However, its rigidity hampers adaptability to changes as any requirement alterations require reiterating earlier phases. In contrast, iterative models like RAD emphasize flexibility and adaptability through repeated cycles of prototyping and testing, allowing for ongoing user feedback and revisions, leading to faster and potentially more aligned developments .