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
4 months agoCarman
4 months agoBrittani
4 months agoAlishia
5 months agoAdelle
5 months agoWayne
5 months agoShakira
5 months agoErinn
5 months agoAlline
6 months agoStephania
6 months agoPatrick
6 months agoAlton
6 months agoTora
6 months agoNikita
10 months agoTonette
10 months agoQuentin
9 months agoArleen
9 months agoGarry
9 months agoRikki
10 months agoMarkus
11 months agoClorinda
9 months agoPearlene
10 months agoYuriko
10 months agoRasheeda
11 months agoVallie
10 months agoCorinne
10 months agoVivan
10 months agoCeola
12 months agoKeneth
10 months agoVesta
11 months agoJenise
11 months agoShakira
11 months agoTula
11 months agoVesta
11 months agoErnie
12 months agoDelpha
12 months agoMing
12 months ago