Why is having stable modules important?

• A. They increase test execution time.
• B. They complicate maintenance.
• C. To reduce flakiness, improve reliability, and speed up maintenance.
• D. They prevent data binding.

Answer: (C)

Stable modules provide predictable behavior and a clean, consistent interface, which is crucial for reliable automated testing. When modules stay stable, tests that depend on them produce consistent results, reducing test flakiness caused by unrelated changes in the UI, data, or environment. This reliability means you can trust test outcomes and maintain confidence in the automation suite.

Stability also speeds up maintenance. If a UI or workflow changes, you update the module in one place rather than touching many tests, keeping test logic clear and easier to manage. Stable modules enable reuse across multiple tests, and you can swap in a better implementation without rewriting tests, further cutting maintenance effort.

While stable modules can indirectly support data binding by offering reliable inputs and outputs, the main benefits are fewer flaky failures, higher reliability, and quicker maintenance.