An airline's frequent flyer's club awards benefits depending on which tier a customer is in. The software must determine which tier to allocate a customer to based on an input value of total Credits Earned to date
Customers initially join the Silver Tier and remain in that tier for the first 400 Credits Earned The next 400 Credits Earned moves the customer into the Gold Tier. The next 600 Credits Earned moves the customer into the Platinum Tier Further Credits Earned moves the customer into the Concierge Tier.
Test Cases have been written with the following total Credits Earned input values:
TC1 -400 Credits
TC2 - 500 Credits
TC3 - 800 Credits
TC4-1500 Credits
Applying the Equivalence Partitioning test design technique, what percentage of valid Equivalence Partitions have these 4 test cases collectively achieved?
Equivalence Partitioning is a black-box test design technique that divides input data of a software module into partitions of equivalent data from which test cases can be derived. In this context, the valid equivalence partitions are:
Silver Tier: 0 to 400 Credits
Gold Tier: 401 to 800 Credits
Platinum Tier: 801 to 1400 Credits
Concierge Tier: 1401+ Credits
The test cases provided cover all these partitions:
TC1 covers the Silver Tier boundary at 400 Credits.
TC2 covers within the Gold Tier at 500 Credits.
TC3 covers the Gold Tier boundary at 800 Credits.
TC4 covers within the Concierge Tier at 1500 Credits.
Since all valid partitions are covered by the test cases, 100% of the valid Equivalence Partitions have been achieved.
Which of the following is NOT an example of a typical risk-based testing activity?
Risk-based testing is an approach to testing that prioritizes and focuses on testing activities based on the level of risk associated with each feature or function of the system under test. Risk-based testing aims to optimize the use of time, resources, and techniques for testing by identifying and addressing the most critical and likely sources of failure or harm in the system under test. Some examples of typical risk-based testing activities are:
Brainstorming sessions are held with a wide variety of stakeholders to identify possible failures in the system: This activity is part of the risk identification process, which involves gathering information and opinions from different perspectives and sources to discover potential risks in the system under test.
Tests are prioritized to ensure that those associated with critical parts of the system are executed earlier: This activity is part of the risk analysis and evaluation process, which involves assessing the probability and impact of each risk and ranking them according to their severity and importance.
The focus of testing is shifted to an area in the system where tests find more defects than expected: This activity is part of the risk mitigation and monitoring process, which involves taking actions to reduce or eliminate the risks and tracking their status and progress.
The evaluation of a risk-management tool to decide which tool to use for future projects is not an example of a typical risk-based testing activity because it is not directly related to testing the system under test based on its risks. Rather, it is an example of a tool selection or evaluation activity, which involves comparing and choosing a tool that can support or enhance the testing process based on criteria such as functionality, usability, reliability, compatibility, cost, etc. You can find more information about risk-based testing in [A Study Guide to the ISTQB Foundation Level 2018 Syllabus], Chapter 3, Section 3.4.
What type of test design technique is the most effective in testing screen-dialog flows?
Where and by whom is Beta testing normally performed?
Beta testing is a type of acceptance testing that is normally performed by customers or potential customers at their own locations. Beta testing is done after the software product has passed the internal testing and quality assurance processes and is ready for release or deployment. Beta testing allows the customers or users to evaluate the software product in their real environment and provide feedback and suggestions for improvement. Beta testing can also help identify defects, compatibility issues, usability problems, or performance bottlenecks that might not have been detected during the internal testing. You can find more information about beta testing in [A Study Guide to the ISTQB Foundation Level 2018 Syllabus], Chapter 2, Section 2.3.
Which of the following BEST describes the relationship between test planning and test execution? [K2]
Gabriele
3 days agoLoise
10 days agoJules
17 days agoEvelynn
25 days agoMiriam
1 month agoAnna
1 month agoTalia
2 months agoJoanna
2 months agoRosendo
2 months agoLayla
2 months agoOmega
3 months agoMaybelle
3 months agoTasia
3 months agoJules
3 months agoEna
4 months agoLindsey
4 months agoMelvin
4 months agoTiffiny
4 months agoDonette
5 months agoShaquana
5 months agoLilli
5 months agoRebecka
5 months agoHaley
5 months agoMarci
6 months agoPaola
6 months agoEva
8 months agoFiliberto
8 months agoChanel
9 months agoDarrin
10 months agoLorriane
10 months agoCyril
11 months agoBrianne
11 months agoTawna
11 months agoMaryanne
12 months agoTommy
12 months agoDomonique
1 year agoWerner
1 year agoDortha
1 year agoRochell
1 year agoAlison
1 year agoChristiane
1 year agoJerry
1 year agoMarta
1 year agoJaclyn
1 year agoBettina
1 year agoPhyliss
1 year agoJenifer
1 year agoRolland
1 year agoLashaun
1 year agoAudra
1 year agoCasie
1 year agoRashad
1 year agoFletcher
1 year agoRonny
1 year agoLanie
1 year agoWilliam
1 year agoEzekiel
1 year agoElenor
1 year agoEladia
1 year agoDarrin
1 year agoTamesha
2 years agoYvonne
2 years agoFranchesca
2 years agoRosendo
2 years agoColette
2 years agoJesusa
2 years ago