Test Smells CTAL-AT Practice Questions (Page 4)

Questions 16–20

1. 16application · medium

   A test method named `testOrderProcessing` performs the following steps: it creates a customer, adds items to a cart, applies a discount, processes payment, and then asserts that the order total is correct. The test is failing intermittently, and the team suspects that the test is doing too much. Which test smell is most likely present, and what refactoring would best address it?

   • AEager Test; split the test into smaller tests, each focusing on a single behavior.
   • BAssertion Roulette; add descriptive messages to each assertion.
   • CGeneral Fixture; simplify the setup to only what is needed for the test.
   • DMystery Guest; replace external dependencies with test doubles.
   Reveal Solution Discussion Select an answer first
2. 17foundation · easy

   Which scenario is most likely to lead to the creation of test smells?

   • AA team that runs tests frequently on a CI server
   • BA team that writes tests incrementally and reviews them regularly
   • CA team that uses a test-driven development approach
   • DA team that copies and pastes test code without adapting it to the new context
   Reveal Solution Discussion Select an answer first
4. 18application · medium

   During a test code review, a tester notices a test method that performs multiple independent verifications: it checks that a login succeeds, then verifies the welcome message, and finally asserts that the user's profile page loads. When the test fails, the tester must examine the test code to determine which verification failed. Which test smell does this test exhibit, and what is the primary consequence?

   • AAssertion Roulette; the test's failure message does not clearly indicate which assertion failed, reducing diagnosability.
   • BGeneral Fixture; the test uses a shared setup that makes it unclear which part of the fixture is relevant.
   • CEager Test; the test verifies too many behaviors, making it difficult to isolate the cause of a failure.
   • DMystery Guest; the test relies on external resources that are not obvious, causing failures to be hard to reproduce.
   Reveal Solution Discussion Select an answer first
5. 19application · medium

   A test method contains several assertions that verify different aspects of a single object's state, but none of the assertions have custom failure messages. When the test fails, the tester cannot tell which assertion failed without debugging. What is the best way to refactor this test to improve diagnosability?

   • ACombine all assertions into a single assertion using a custom matcher.
   • BSplit the test into multiple tests, each with a single assertion.
   • CRemove the assertions that are not essential.
   • DAdd descriptive failure messages to each assertion.
   Reveal Solution Discussion Select an answer first
6. 20foundation · easy

   Which technique is most effective for detecting test smells in existing test code?

   • APerforming a code review focused on test code quality
   • BIncreasing the number of test cases
   • CRunning the tests in a different environment
   • DRunning the tests with a code coverage tool
   Reveal Solution Discussion Select an answer first