A test manager decided to skip static testing since he believes bugs can be found easily by doing dynamic testing. Was this decision right or wrong?
Correct Answer: B
Static testing is a form of testing that does not involve executing the software or system under test. It includes activities such as reviews, inspections, walkthroughs, and analysis of documents, code, and models. Static testing can find defects early in the development process, before they become more expensive and difficult to fix in later stages. Static testing can also improve the quality of the software or system by preventing defects from being introduced in the first place. Static testing can complement dynamic testing, which involves executing the software or system under test and checking the results against expected outcomes. Dynamic testing can find defects that static testing may miss, such as performance, usability, or integration issues. However, dynamic testing alone is not sufficient to ensure quality, as it may not cover all possible scenarios, inputs, or paths. Therefore, a test manager who decides to skip static testing is making a wrong decision, as he or she is ignoring the benefits of static testing and relying solely on dynamic testing, which may not be effective or efficient enough to find andprevent defects. References = ISTQB Certified Tester Foundation Level Syllabus, Version 4.0, 2018, Section 2.1.1, page 14; ISTQB Glossary of Testing Terms, Version 4.0, 2018, page 36; ISTQB CTFL 4.0 - Sample Exam - Answers, Version 1.1, 2023, Question 3, page 9.
Question 62
Which ONE of the following is a GOOD testing practice that is INDEPENDENT of the chosen SDLC (Software Development Life Cycle) model?
Correct Answer: D
Different test levels (unit, integration, system, acceptance) have specific objectives while sometimes overlapping to ensure comprehensive testing (D). Option A contradicts shift-left principles, B encourageslate testing (which is ineffective), and C incorrectly assumes that all development activities require direct test actions.
Question 63
Shripriya is defining the guidelines for the review process implementation in her company. Which of the following statements is LEAST likely to have been recommended by her?
Correct Answer: C
In a structured review process, it is essential to plan reviews carefully and manage them effectively. Reviewing large work products in one go is not recommended because it can lead to oversight of issues due to fatigue or information overload. It is more efficient to break down large work products into smaller, manageable parts and review them incrementally. This ensures a thorough and effective review process. Additionally, other practices such as planning for the review, starting discussions during review initiation, and creating defect reports for found issues are standard recommendations for an effective review process. Top of Form Bottom of Form
Question 64
Which of the following statements is true?
Correct Answer: B
Non-functional testing includes testing of both technical and non-technical quality characteristics. Non-functional testing is the process of testing the quality attributes of a system, such as performance, usability, security, reliability, etc. Non-functional testing can be applied at any test level and can use both black-box and white-box test techniques. Non-functional testing can cover both technical aspects, such as response time, throughput, resource consumption, etc., and non-technical aspects, such as user satisfaction, accessibility, compliance, etc. Therefore, option B is the correct answer.
Question 65
Which of the following statements about the test pyramid is true?
Correct Answer: B
The test pyramid is a concept that illustrates the different levels of testing and their relative quantities. The pyramid suggests that there should be more low-level unit tests than high-level end-to-end tests. As you move up the pyramid, the scope of each test increases, meaning each higher level test typically covers more of the production code. * Unit Tests: Form the base of the pyramid and cover individual units of code. They are numerous because they are quick to write and execute. * Service/Integration Tests: Sit in the middle of the pyramid and cover interactions between integrated units or services. * UI/End-to-End Tests: At the top of the pyramid, these tests cover entire workflows and user interactions, making them fewer in number due to their complexity and execution time. Option B accurately describes that the higher the layer of the test pyramid, the more production code a single automated test tends to cover because these higher-level tests involve broader functionalities and interactions compared to unit tests.
