What is the recommended practice for modules in Tosca XScan?

• A. Use Standard Module when possible
• B. Avoid standard modules due to maintenance
• C. Create modules ad-hoc for every test
• D. Use only custom modules

Answer: (A)

The idea behind XScan modules is to maximize reuse and keep maintenance light. Using a Standard Module whenever possible gives you a ready-made, reusable abstraction for common UI elements that can be shared across many tests. This centralizes changes—if a UI control changes, you update the standard module once and all tests that rely on it benefit—so you avoid duplicating work across ad-hoc modules. Creating modules ad-hoc for every test leads to duplication and a maintenance burden as UI elements evolve. Relying solely on custom modules misses the efficiency and consistency that standard modules provide, so they’re not the recommended path.