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

Questions 16–20

1. 16foundation · easy

   How do testers contribute to code quality in an agile team?

   • ABy providing feedback on testability and potential code smells during development
   • BBy ensuring that the code is written in a specific style
   • CBy only reporting defects after the code is complete
   • DBy writing all the documentation for the code
   Reveal Solution Discussion Select an answer first
2. 17expert · hard

   A team has accumulated significant technical debt over several sprints. The codebase is becoming difficult to modify and test, and the team is spending more time fixing defects than adding new features. The product owner is reluctant to allocate time for refactoring because it does not deliver new functionality. What is the most effective way for the tester to advocate for addressing technical debt?

   • AQuantify the impact of technical debt in terms of increased testing effort and defect rates, and propose a regular refactoring timebox.
   • BAsk the developers to work overtime to refactor the code without affecting the sprint backlog.
   • CRefuse to test any new features until the technical debt is resolved.
   • DRefactor the code in secret during testing activities to avoid disrupting the sprint plan.
   Reveal Solution Discussion Select an answer first
4. 18expert · hard

   An agile team is under pressure to deliver a new feature by the end of the sprint. The developer proposes taking a shortcut that introduces a known design flaw, arguing that it can be refactored later. The tester is concerned about the impact on testability and future maintenance. The product owner is focused on meeting the deadline. What is the most effective way for the tester to address this situation?

   • AAccept the shortcut and write a comprehensive set of regression tests to ensure the flaw does not cause issues.
   • BCollaborate with the developer to quantify the technical debt and agree on a follow-up story to refactor it in the next sprint.
   • CInsist that the feature be implemented without any shortcuts, even if it means the sprint goal is not met.
   • DEscalate the issue to management and request that the feature be delayed until the design is corrected.
   Reveal Solution Discussion Select an answer first
5. 19expert · hard

   A team is working on a module that has a large class with many responsibilities. The class is difficult to test because tests must set up many dependencies and the class has many methods. The team wants to improve testability. What is the most effective refactoring approach?

   • AUse a mocking framework to mock all the dependencies in tests.
   • BExtract classes for each responsibility and use dependency injection to connect them.
   • CWrite a test that uses the class's public API without setting up all dependencies.
   • DAdd more tests to cover the existing class, even if they are complex to set up.
   Reveal Solution Discussion Select an answer first
6. 20application · medium

   A team is using a static analysis tool in their CI pipeline. The tool reports a high number of warnings, but the team has been ignoring them because the build still passes. The tester wants to ensure that code quality issues are addressed. Which action would be most effective?

   • ADisable the static analysis tool to reduce noise and allow developers to focus on writing tests.
   • BConfigure the build to fail on new warnings while allowing existing warnings to be tracked separately.
   • CIncrease the threshold for warnings so that the build only fails on critical issues.
   • DAsk developers to manually review the warnings at the end of each sprint.
   Reveal Solution Discussion Select an answer first