Objective: Apply Layering of Test Automation Frameworks CTAL-TAE Practice Questions (Page 2)

Questions 6–10

1. 6application · medium

   A test automation framework currently has a class called 'TestBase' that handles WebDriver initialization, takes screenshots on failure, and also contains methods like 'loginAsAdmin' and 'createReport'. The team is experiencing maintenance issues because changes to reporting logic affect login methods. What is the best way to refactor this to improve separation of concerns?

   • AMove all methods into the test case layer so that each test can call them directly.
   • BCreate a single utility class that contains all methods, but make them static for easy access.
   • CKeep TestBase as is, but use inheritance so that test classes can override the methods they need.
   • DSplit TestBase into separate classes: a technical layer class for driver and reporting, and a functional layer class for login and report creation actions.
   Reveal Solution Discussion Select an answer first
2. 7foundation · easy

   What is the primary role of the business layer in a layered test automation framework?

   • ATo abstract business processes and workflows from technical details.
   • BTo execute individual test cases and report results.
   • CTo manage low-level driver initialization and browser options.
   • DTo store test data in external files for reuse.
   Reveal Solution Discussion Select an answer first
4. 8expert · hard

   A test automation framework has a functional layer with a method 'login(user, password)'. The business layer has a method 'loginAsAdmin()' that calls 'login' with admin credentials. A new requirement asks to support multiple user roles (admin, user, guest). What is the most maintainable way to extend the framework?

   • AAdd a parameter 'role' to the business layer method, e.g., 'loginAs(role, user, password)', and keep the functional layer method unchanged.
   • BPut the role-based login logic in the test case layer, so that each test can specify the role.
   • CCreate separate functional layer methods for each role, e.g., 'loginAsAdmin', 'loginAsUser', 'loginAsGuest'.
   • DModify the existing 'loginAsAdmin' method to accept a role parameter, and have it call the functional layer with the appropriate credentials.
   Reveal Solution Discussion Select an answer first
5. 9foundation · easy

   What does the principle of separation of concerns mean in the context of a layered test automation framework?

   • AEach layer should have a distinct responsibility and minimal overlap with other layers.
   • BThe framework should use separate tools for each layer.
   • CAll layers should be combined into a single module to reduce complexity.
   • DEach test case should be independent and not share any code.
   Reveal Solution Discussion Select an answer first
6. 10application · medium

   A test automation team is refactoring a fragile Selenium framework. Currently, test scripts directly instantiate WebDriver, call driver.findElement() with CSS selectors, and also contain business steps like 'login as admin'. The team wants to apply separation of concerns so that a change to the application's login page locators does not force changes to test cases. Which refactoring approach best achieves this?

   • AKeep test scripts as they are but add a configuration file for the application URL so that environment changes do not require code edits.
   • BCreate a single utility class that contains both driver management and business workflow methods, and have test cases call that class.
   • CMove all WebDriver instantiation and element location into a technical layer, and create a business layer with methods like loginAsAdmin() that test cases call.
   • DUse page object classes for each page but keep the login steps inline in test cases, since page objects already encapsulate locators.
   Reveal Solution Discussion Select an answer first