Aspects of Code Quality CT-ATT Practice Questions (Page 2)

Questions 6–10

1. 6application · medium

   A developer is about to refactor a class to improve its design. The class has a suite of unit tests that currently pass. What is the most important thing the developer should do before and during the refactoring to ensure the refactoring is safe?

   • ARewrite all the unit tests to match the new design before starting the refactoring.
   • BRun the existing unit tests frequently to verify that behavior remains unchanged.
   • CRefactor the code and the tests simultaneously to keep them in sync.
   • DDelete any tests that are difficult to understand to make the refactoring easier.
   Reveal Solution Discussion Select an answer first
2. 7expert · hard

   A team is developing a microservice that processes financial transactions. The code is highly efficient and performs well, but it is written in a style that is difficult to read and understand. The tester is finding it hard to create meaningful test cases because the logic is obscured. The product owner is satisfied with the performance and does not want to delay the release. What is the best course of action?

   • AWrite tests that use the public API without needing to understand the internal logic.
   • BKeep the code as is and rely on performance testing to ensure correctness.
   • CAsk the developer to add comments to explain the complex logic.
   • DRefactor the code to improve readability, even if it slightly reduces performance, and add tests to verify behavior.
   Reveal Solution Discussion Select an answer first
4. 8application · medium

   A tester on an agile team notices that a frequently modified class has a method with 15 parameters, many of which are only used in one branch. The team has no automated tests for this method, and adding them is difficult because constructing valid argument combinations is complex. Which action would best address the root cause of the testability problem?

   • AAdd a unit test that uses reflection to invoke the method with default values for unused parameters.
   • BRefactor the method by extracting cohesive sub-methods and introducing parameter objects.
   • CAdd a static analysis rule to flag methods with more than 10 parameters.
   • DIncrease code coverage by writing an integration test that exercises the method through the user interface.
   Reveal Solution Discussion Select an answer first
5. 9expert · hard

   A team is working on a legacy module that has poor testability. The module has a complex dependency on a database and a file system, and the existing tests are slow and unreliable. The team wants to improve testability without a full rewrite. What is the most effective approach?

   • AUse a static analysis tool to identify the complex dependencies and document them.
   • BIntroduce dependency injection and use test doubles (mocks/stubs) to isolate the module from external dependencies.
   • CRefactor the module into smaller classes, but keep the dependencies as they are.
   • DWrite more integration tests that use the real database and file system to ensure accuracy.
   Reveal Solution Discussion Select an answer first
6. 10foundation · easy

   Which code quality attribute is most directly related to testability?

   • AEfficiency
   • BSecurity
   • CReadability
   • DModularity
   Reveal Solution Discussion Select an answer first