which statement about test approaches is TRUE7
SELECT ONE OPTION
The statement that is true about test approaches is that in a Model-based test approach, tests can be created automatically. This is confirmed by the understanding that model-based testing involves generating test cases directly from a model that describes the system functions, behavior, or both, which supports automatic test creation.
The following user story has been written for a new application being developed to pre-book a space at a National Car Park.
As a vehicle driver
i want to be able to pre-book a car parking space online, selecting a disabled driver's space if needed
So that l can pay in advance and receive confirmation of my parking space number.
The following acceptance criteria have also been written:
* Payment can be made via PayPal, Debit or Credit Card
* Confirmation of payment and car parking details should be sent after the booking process is completed
* Driver information is stored in the reservation database
The database has been built and tested in a previous sprint, but the interface to the different payment methods have yet to be developed
As a tester in an agile team, you have been asked to review the user story You have detected some issues with this story:
1. it needs to cater for different user groups: a driver or disabled driver
2. it needs to cater for different vehicle types: a car. 4x4. van or motorbike
3. There are no acceptance criteria relating to how quick the booking process should be
4. How confirmation is to be sent for payment and space number, and other important details, have not been specified
5. A stub will be needed to test the payment method
Which pair of requirements engineering techniques are you MOST LIKELY to have used to uncover these issues'
SELECT ONE OPTION
The most likely pair of requirements engineering techniques used to uncover the issues mentioned with the user story would be 'Storyboards and Personas.' This approach allows for a visual and persona-based exploration of how different users (such as drivers of different vehicle types and disabled drivers) would interact with the system. This technique helps in uncovering varied user needs and ensuring that all critical user interactions are considered during the development process.
BestFor Incorporated is a rapidly growing online financial services company that offers guidance to its customers on a range of financial products. Its first website, BestForMortgages, was launched two years ago, shortly followed by BestForPensions. The popularity of both sites has driven the company to expand its offerings into other sectors and a third website, BestForFood, has recently been released.
The first two websites have proven to be functionally robust but suffered from performance issues due to:
Underestimation of concurrent user access at peak times in its original operational profiles
Data volumes rapidly growing beyond expectations on a single database shared by both sites.
All three websites share the same web server.
The BestForFood system has been running live for several months, however the following significant non-functional defects have been recorded:
A) The layout and navigation of the BestForFood website was not considered by the users as consistent with BestForPensions and BestForMortgages
B) Soon after delivering the BestForFood system the performance of both BestForPensions and BestForMortgages noticeably slowed
C) The time taken to diagnose, repair and re-test production defects did not meet BestForFood service level agreements
D) BestForFood performance was adversely impacted by unexpected growth in data volumes
E) The time taken to install monthly builds into the production system exceeded agreed timescales.
Which TWO of these defects might have been prevented had portability testing and compatibility testing been employed?
Analysis:
The significant non-functional defects recorded for the BestForFood system indicate issues that could be mitigated by appropriate non-functional testing strategies:
Portability Testing:
Ensures that the application can operate in different environments without issues. This could have addressed the defect related to the layout and navigation consistency across different websites (Defect A).
Compatibility Testing:
Ensures that the application works well with other systems and environments. This could have helped in preventing the performance issues noticed in the BestForPensions and BestForMortgages websites after the deployment of BestForFood (Defect B).
Explanation of Incorrect Options:
C . The time taken to diagnose, repair and re-test production defects: This is more related to maintainability and operational processes.
D . BestForFood performance impacted by data growth: This is better addressed through performance and scalability testing.
E . Installation time exceeding agreed timescales: This is related to deployment and operational efficiency.
The ISTQB CTAL-TTA syllabus and standard non-functional testing practices emphasize the importance of portability and compatibility testing for ensuring smooth operation across different environments and systems.
Sources:
ISTQB-CTAL-TTA Syllabus
General knowledge on non-functional testing practices.
Below is pseudo-code which calculates a customer's cruise credits based on past cruise history:
PROGRAM CALC CRUISE CREDITS (CUST_ID) COUNT_CRUISES, CRUISE_CREDITS, LOYALTY_RATING: INTEGER CRUISE_LENGTH, CRUISE_ACCOM_TYPE: VAR
LOYALTY_RATING = 0
COUNT_CRUISES = 0
CRUISE_LENGTH = 0
CRUISE_ACCOM_TYPE = 0
BEGIN
READ CUSTOMER'S CRUISE HISTORY TO OBTAIN COUNT OF CRUISES
READ CRUISE_HISTORY (CUST_ID)
WHILE COUNT_CRUISES != -1 DO
READ CUSTOMER'S NEXT CRUISE
READ NEXT_CRUISE
IF CRUISE_ACCOM_TYPE = 3 THEN
CRUISE_CREDITS = CRUISE_CREDITS + 5
ELSE
IF CRUISE_ACCOM_TYPE = 2 THEN
CRUISE_CREDITS = CRUISE_CREDITS + 3
ELSE
CRUISE_CREDITS = CRUISE_CREDITS + 2
ENDIF
ENDIF
COUNT_CRUISES = COUNT_CRUISES - 1
ENDWHILE
LOYALTY_RATING = CRUISE_CREDITS / COUNT_CRUISES
WRITE ("CRUISE CREDIT TOTAL IS:")
WRITE (CRUISE_CREDITS)
END PROGRAM CALC CRUISE CREDITS
The code contains data flow anomalies on lines 14 and 27. Which examples of data flow anomalies can be found on these lines?
In the pseudo-code provided, we need to identify data flow anomalies, which typically occur when variables are used improperly in terms of their definition, usage, or re-definition.
Analyzing the pseudo-code step by step:
Lines 1-4 initialize variables LOYALTY_RATING, COUNT_CRUISES, CRUISE_LENGTH, and CRUISE_ACCOM_TYPE to 0.
Lines 6-7 read the customer's cruise history.
Line 8 begins a WHILE loop that continues until COUNT_CRUISES is -1.
Lines 9-10 read the next cruise.
Lines 11-19 check the CRUISE_ACCOM_TYPE and update CRUISE_CREDITS accordingly.
Line 20 decrements COUNT_CRUISES.
Line 21 ends the WHILE loop.
Line 22 calculates LOYALTY_RATING by dividing CRUISE_CREDITS by COUNT_CRUISES.
Lines 23-24 output the CRUISE_CREDITS.
Line 25 ends the program.
Data Flow Anomalies:
Line 14: CRUISE_CREDITS is re-defined before being used.
The initial problem here is that CRUISE_CREDITS should be assigned a value before it is incremented in lines 12, 15, and 17. The code does not show any prior definition (initialization) for CRUISE_CREDITS before these increments.
Line 27: LOYALTY_RATING is defined but not subsequently used.
After LOYALTY_RATING is calculated in line 22, it is not used again. This means the calculated value serves no purpose in the program as it stands.
By considering the above points, we can confirm that the correct option is C:
Line 14: CRUISE_CREDITS is re-defined before being used (it should have been initialized before the WHILE loop or just before its first usage inside the loop).
Line 27 (Line 22 in provided pseudo-code): LOYALTY_RATING is defined (calculated) but not subsequently used.
This matches the reference provided in the ISTQB sample exam answers, confirming that C is the correct answer.
ISTQB CTAL-TTA Sample Exam Questions
ISTQB Exam Structures and Rules
ISTQB CTAL-TTA Sample Exam Answers
ISTQB-CTAL-TTA Syllabus
ISTQB Exam Structure Tables
A unit test should be isolated Which option correctly describes the meaning of 'isolated' as a characteristic of a unit test?
SELECT ONE OPTION
Whenever it is run under the same conditions, it should produce the same results.
The term 'isolated' as a characteristic of a unit test means that it should test only the code for which it was originally written. This ensures that the unit test is focused, minimizes dependencies on other parts of the codebase, and errors can be traced back to specific units without ambiguity .
Gaston
7 days agoSheridan
14 days agoSamira
21 days agoAide
30 days agoLillian
1 month agoLaurel
1 month agoEden
2 months agoRia
2 months agoDorothea
2 months agoTalia
2 months agoNguyet
3 months agoKallie
3 months agoAnna
3 months agoPok
3 months agoLawana
4 months agoViola
4 months agoShantay
4 months agoDaniela
4 months agoMerlyn
5 months agoJanessa
5 months agoMagdalene
5 months agoPeggie
5 months agoGertude
6 months agoJacinta
6 months agoWinfred
6 months agoSoledad
6 months agoCarmen
7 months agoGracia
7 months agoCarri
7 months agoDaren
9 months agoEve
9 months agoDenae
9 months agoAlva
10 months agoGraham
10 months agoJoanne
10 months agoVan
11 months agoJill
11 months agoTimmy
1 year agoArminda
1 year agoBuck
1 year agoStefany
1 year agoEliz
1 year agoGerry
1 year agoKimberely
1 year agoOtis
1 year agoBeckie
1 year agoAntonio
1 year agoRaul
1 year agoStarr
1 year agoSerina
1 year agoMerri
1 year agoBrice
1 year agoMarci
1 year agoRosamond
1 year agoAaron
1 year agoRosendo
1 year agoStacey
1 year agoReiko
1 year agoTiera
1 year agoGilma
1 year agoAhmed
1 year agoCarey
1 year agoPamella
2 years agoRoxane
2 years agoKami
2 years agoEarleen
2 years agoTennie
2 years agoMatthew
2 years agoKris
2 years agoMicaela
2 years agoAshanti
2 years agoMiles
2 years agoAntonio
2 years agoBlair
2 years agoRodney
2 years agoRoxanne
2 years agoCasey
2 years ago