Consider the following specification:

If you are flying with an economy ticket, there is a possibility that you may get upgraded to business class, especially if you hold a gold card in the airline's frequent flier program. If you don't hold a gold card, there is a possibility that you will get 'bumped' off the flight if it is full when you check in late.
This is shown in the control flow graph below. Note that each box (i.e., statement, decision) has been numbered.
Three tests have been run:
Test 1: Gold card holder who gets upgraded to business class
Test 2: Non-gold card holder who stays in economy
Test 3: A person who is bumped from the flight
What is the level of decision coverage achieved by these three tests?
Stress testing is the most appropriate method for identifying weak areas in code that may cause performance issues, especially under conditions of extreme load or stress. This type of testing deliberately pushes the system beyond its normal operational capacity to see how it behaves under stress, which can help reveal vulnerabilities in error recovery and transactional integrity that are not apparent under normal conditions. Stress testing can provide early insights into potential failure points and help prioritize areas for improvement before full-scale deployment.
Floyd
3 months agoCarman
3 months agoBrittani
3 months agoAlishia
4 months agoAdelle
4 months agoWayne
4 months agoShakira
4 months agoErinn
4 months agoAlline
5 months agoStephania
5 months agoPatrick
5 months agoAlton
5 months agoTora
5 months agoNikita
9 months agoTonette
9 months agoQuentin
8 months agoArleen
8 months agoGarry
8 months agoRikki
9 months agoMarkus
10 months agoClorinda
8 months agoPearlene
9 months agoYuriko
9 months agoRasheeda
10 months agoVallie
9 months agoCorinne
9 months agoVivan
9 months agoCeola
11 months agoKeneth
9 months agoVesta
10 months agoJenise
10 months agoShakira
10 months agoTula
10 months agoVesta
10 months agoErnie
11 months agoDelpha
11 months agoMing
11 months ago