Decision table testing is being performed on tran-sactions in a bank’s ATM (Automated Teller Machine) system. Two test cases have already been generated for rules 1 and 4. which are shown below:
SEE ATTACHMENT 1
Given the following additional test cases: SEE ATTACHMENT 2
Which two of the additional test cases would achieve full coverage of the full decision table (when combined with the test cases that have already been generated for rules 1 and 4)?
Correct Answer:
C
Decision table testing is used to analyze combinations of inputs to determine the appropriate outputs, often based on specific rules or conditions.
For the problem statement:
✑ Rule 1: (Withdrawal = Allowed, Balance = Sufficient, Fast Cash = True, Correct PIN = True)
✑ Rule 4: (Withdrawal = Allowed, Balance = Sufficient, Fast Cash = True, Correct
PIN = False)
The additional test cases are:
✑ DT1: (Withdrawal = Allowed, Balance = Insufficient, Fast Cash = True, Correct PIN
= True)
✑ DT2: (Withdrawal = Allowed, Balance = Sufficient, Fast Cash = False, Correct PIN
= True)
✑ DT3: (Withdrawal = Allowed, Balance = Insufficient, Fast Cash = True, Correct PIN
= False)
✑ DT4: (Withdrawal = Allowed, Balance = Sufficient, Fast Cash = False, Correct PIN
= False)
From the given test cases, DT2 covers the scenario where Fast Cash is False, which is not covered in the initial cases. DT3 covers the case where Balance is Insufficient and PIN is incorrect.
Combining Rules 1 and 4 with DT2 and DT3 covers all the scenarios. References:
✑ Certified Tester Foundation Level v4.0
✑ 10 Sample Exams ISTQB Foundation Level (CTFL) v4.0
Which of the following does MOT describe a reason why testing is necessary?
Correct Answer:
B
Testing is necessary for various reasons, such as:
✑ To detect defects and failures that may affect the quality, performance, reliability or security of a software product or system
✑ To verify that a software product or system meets its specified requirements, expectations and standards
✑ To validate that a software product or system fulfills its intended purpose and satisfies its stakeholders’ needs
✑ To provide information and feedback about the status and risks of a software product or system
✑ To comply with regulations or contractual obligations that mandate testing for certain types of software products or systems The following statements describe some reasons why testing is necessary:
✑ A) The customer decided that 100% branch coverage shall be achieved. This is a reason why testing is necessary, as it reflects a contractual obligation or a quality standard that requires testing to measure and achieve a certain level of code coverage.
✑ C) For avionics and pharmaceutical systems software testing is mandated by standards. This is a reason why testing is necessary, as it reflects a regulation or a compliance requirement that mandates testing for certain types of software products or systems that have high safety or security risks.
✑ D) The risks associated with delivering the system are far higher than the cost of testing. This is a reason why testing is necessary, as it reflects a risk-based approach that considers testing as an investment to reduce the probability and impact of potential failures or defects. The following statement does not describe a reason why testing is necessary:
✑ B) The acquisition of test automation tools was based on the assumption that it will be used m all projects. This is not a reason why testing is necessary, as it reflects a business decision or a resource allocation that does not justify the need or purpose of testing. Test automation tools are not always suitable or beneficial for all projects, and testing can be performed with or without test automation tools. Verified References: [A Study Guide to the ISTQB® Foundation Level 2018 Syllabus - Springer], Chapter 1, page 5-6.
A software calculates the annual car tax using three inputs:
- E; the emission level of the vehicle
- P: the power of the vehicle
-T the type of the vehicle
The input value for P can be integer positive values between 15 and 350.
Which of the following answers contains a correct list of a boundary values for the P input?
Correct Answer:
B
A correct list of boundary values for the P input should include the minimum and maximum values of the valid range (15 and 350), as well as the values just below and above the boundaries (14 and 351). Boundary value analysis is a test design technique that involves testing the values at or near the boundaries of an input domain or output range, as these values are more likely to cause errors than values in the middle. Option B satisfies this condition, as it has all four boundary values (14, 15, 350, 351). Option A has only two boundary values (14 and 351), option C has only two boundary values (15 and 350), and option D has no boundary values at all. Verified References: A Study Guide to the ISTQB® Foundation Level 2018 Syllabus - Springer, page 34.
Consider the following statements about risk-based testing.
I) Risk-based testing has the objective to reduce the level of protect risks.
II) Tests should be prioritized to find tie critical detects as early as possible.
III) Non-testing activities may also help to reduce risk
IV) Risks have to be reassessed on a regular basis.
V) The project stakeholders can give useful input to determine the risks
Correct Answer:
B
The following statements about risk-based testing are correct:
✑ II) Tests should be prioritized to find tie critical detects as early as possible. Risk- based testing involves prioritizing tests based on risk level, which reflects both the likelihood and impact of defects or failures. Tests with higher risk level should be executed earlier than tests with lower risk level, in order to find and fix critical defects as soon as possible.
✑ III) Non-testing activities may also help to reduce risk. Risk-based testing does not
only involve testing activities, but also other activities that can help mitigate risks, such as reviews, inspections, audits, simulations or prototyping.
Which type of software development product can undergo static testing?
Correct Answer:
A
Static testing is a form of testing that does not involve executing the software, but rather analyzing it for defects, errors, or violations of standards. Static testing can be applied to any software development product, including requirements specifications, design specifications, code, test cases, test plans, user manuals, etc. Static testing can be done by using various techniques such as reviews, inspections, walkthroughs, checklists, static analysis tools, etc. Verified References: A Study Guide to the ISTQB® Foundation Level 2018 Syllabus - Springer, page 7.
