Which of the following examples represents System Integration testing?
Answer : A
System Integration Testing (SIT) involves testing the interactions between different systems or components. Testing an e-commerce website's integration with a third-party payment gateway is an example of SIT, as it checks the correct functioning of the integrated systems. This ensures that the e-commerce platform can successfully interact with external systems to process payments.
ISTQB CTFL Syllabus V4.0, Section 2.2.2 on system integration testing.
Which of the following statements is CORRECT about the value added by a tester to release planning?
Answer : B
During release planning, a tester adds value by assessing the testability of user stories. This involves evaluating whether the user stories are clear, concise, and testable. The tester ensures that the acceptance criteria are well-defined and that the stories can be effectively tested within the given timeframe.
ISTQB CTFL Syllabus V4.0, Section 5.1.2 on the tester's contribution to iteration and release planning, which includes assessing the testability of user stories.
Which of the following is a good testing practice which is applicable INDEPENDENT of the software development lifecycle followed?
Answer : B
Independent of the software development lifecycle followed, it is a good practice to ensure that each test level (e.g., unit testing, integration testing, system testing) has clear and appropriate objectives. This ensures that the testing is focused and effective at each level. Other options either contradict good practices or are not applicable across all lifecycle models.
ISTQB CTFL Syllabus V4.0, Section 1.4.1 on test levels and objectives, emphasizing the importance of defining clear test objectives for each level of testing.
What does the "absence-of-defects fallacy" refer to in software development?
Answer : A
The 'absence-of-defects fallacy' in software development refers to the mistaken belief that if a software system has been thoroughly tested and all requirements have been met without any defects, it guarantees the success of the system. However, this is not necessarily true. Even if no defects are found, the system might still fail to meet the user's needs or business objectives. This fallacy highlights the importance of validation in addition to verification to ensure that the system fulfills the intended use and requirements.
Consider a program that computes the factorial of a number (n). From the specifications you know that:
* If n < 0, a message "Value out of range" must be issued.
* If 0 < n < 100, the program calculates the factorial and returns the number
* If 100 < n < 200 message "Value out of range" must be issued
Which of the following statements about the equivalence partitions is CORRECT?
Answer : C
Equivalence partitioning involves dividing input data into partitions that are treated the same by the system under test. The given specifications create overlapping partitions:
For n<0n < 0n<0, an error message 'Value out of range' is issued.
For 0<n<1000 < n < 1000<n<100, the factorial is calculated.
For 100<n<200100 < n < 200100<n<200, the same error message 'Value out of range' is issued.
However, the range between 0 and 100 is exclusive of 0 and 100, meaning that the partitions overlap and create ambiguity for the boundary values. Thus, the correct statement is that the requirements are not correct because the partitions are overlapping.
Which ONE of the following is a CORRECT example of the purpose of a test plan?
Answer : B
A test plan serves multiple purposes, such as defining the scope, approach, resources, and schedule of the testing activities. It also helps in communicating important information and managing stakeholder expectations. In agile projects, test plans might be concise to align with agile principles of simplicity and flexibility. A one-page test plan can effectively communicate broad activities and strategic decisions, such as not writing detailed test cases due to the project's agile nature. This approach ensures that essential information is conveyed without unnecessary documentation overhead, adhering to the agile manifesto's value of 'working software over comprehensive documentation'.
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?
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