I'm stumped, but I'm going to go with D. Logging the failure seems like the most logical outcome. Although, I do wonder if the test object's name is a subtle clue...
Haha, I bet the developer who wrote this test has a great sense of humor. 'Risk level HARMLESS, duration SHORT' - that's the kind of quality assurance I can get behind!
D seems right to me. The test log is where you'd want to see the details if something goes wrong with the assert. Doesn't make much sense to just silently fail or add it to some variant.
D seems right to me. The test log is where you'd want to see the details if something goes wrong with the assert. Doesn't make much sense to just silently fail or add it to some variant.
D seems right to me. The test log is where you'd want to see the details if something goes wrong with the assert. Doesn't make much sense to just silently fail or add it to some variant.
The correct answer is clearly D. The test will log a message if the assert_equals method parameters don't match. That's the whole point of using it in the first place.
Sabra
6 months agoBernardine
5 months agoSheldon
5 months agoBettina
5 months agoLauna
6 months agoNancey
6 months agoAlpha
6 months agoTresa
6 months agoLindsey
6 months agoShannon
5 months agoDonte
5 months agoMacy
5 months agoFlorinda
6 months agoThaddeus
6 months agoLayla
6 months agoKarl
6 months agoLauna
6 months agoNancey
6 months agoLoren
6 months agoKatina
6 months agoSherell
6 months agoCassi
6 months agoPage
6 months agoGlory
7 months agoRonnie
6 months agoSheldon
6 months agoLoreta
6 months agoDomonique
6 months ago