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 one of the following is an example of how product risk analysis can influence the testing approach?
The other options are not examples of how product risk analysis can influence the testing approach, because they are either not related to product risks or not based on risk levels. They are:
Tests have been specified for the latest software release and users have prioritised these
However, there are some dependencies between tests as shown in the table below (e.g. Test ID. X cannot be run until Test ID. Y has been successfully completed).
Which test execution schedule best meets the prioritisation and dependency conditions?
The test execution schedule should follow the priority order of the tests, as well as the dependency constraints. The priority order is given by the user value column, where higher values indicate higher priority. The dependency constraints are given by the dependency column, where a test ID indicates that the test cannot be run until the test with that ID has been successfully completed. Therefore, the test execution schedule should start with the highest priority test that has no dependency, which is test 5. Then, it should continue with the next highest priority test that has no dependency or has a satisfied dependency, which is test 1. Then, it should proceed with test 2, which depends on test 1, and then test 3, which depends on test 2. Finally, it should end with test 4, which depends on test 3. Thus, the test execution schedule that best meets the prioritisation and dependency conditions is 5,1,2,3,4.
Which of the types of test tools noted below BEST describes tools that support reviews?
Tools for document review and annotation
Tools for document comparison and version control
Tools for checklist management and defect tracking
Tools for recording user actions and feedback
Tools for analyzing user behavior and satisfaction
Tools for simulating different user interfaces and devices
Tools for data validation and verification
Tools for data cleansing and transformation
Tools for data profiling and analysis
Tools for security testing
Tools for performance testing
Tools for accessibility testing
You are responsible for applying the correct technique (or a review of the requirements document for a project to develop a new software application. You identify the reviewers and the required roles, including the meeting leader, who is the requirements document author, and a separate role for a scribe. Additionally, you decide to take a relatively informal approach to the requirements review. The goal of the review is to find defects in the requirements document, such as omissions, inconsistencies, and duplications. Another goal of the review is to improve the software application's usability and accessibility by considering the various stakeholders' viewpoints.
Which of the following statements BEST describes this scenario?
This scenario is using a walkthrough review type and a perspective-based review technique. A walkthrough is a type of review that is relatively informal and led by the author of the work product. A perspective-based review technique is a technique that involves reviewing the work product from different viewpoints or perspectives of various stakeholders. The scenario matches these descriptions, as it involves an informal approach, a meeting leader who is the author of the requirements document, and a goal of improving the software application's usability and accessibility by considering the various stakeholders' viewpoints. Option A is incorrect, as a pair review is a type of review that involves only two people, usually the author and another team member. Option C is incorrect, as a checklist-based review technique is a technique that involves reviewing the work product against a predefined list of items or criteria. Option D is incorrect, as it combines the incorrect descriptions of options A and C.
Domonique
7 days agoWerner
22 days agoDortha
24 days agoRochell
1 months agoAlison
1 months agoChristiane
2 months agoJerry
2 months agoMarta
2 months agoJaclyn
2 months agoBettina
3 months agoPhyliss
3 months agoJenifer
3 months agoRolland
3 months agoLashaun
3 months agoAudra
4 months agoCasie
4 months agoRashad
4 months agoFletcher
4 months agoRonny
5 months agoLanie
5 months agoWilliam
5 months agoEzekiel
5 months agoElenor
5 months agoEladia
6 months agoDarrin
6 months agoTamesha
6 months agoYvonne
7 months agoFranchesca
8 months agoRosendo
8 months agoColette
8 months agoJesusa
9 months ago