Why are ATF tests and suites disabled by default?

Why are ATF tests and suites disabled by default?

• A. They should only be run in non-production instances
• B. They require admin rights
• C. They are deprecated
• D. They run only on weekends

Answer: (A)

ATF tests and suites are disabled by default because automated tests can affect live users and production data if they run there. They’re designed to be executed in non-production environments—like development or testing environments—where you have control over the data, states, and timing of the test runs. Running ATF in production could cause unintended changes, performance impacts, or user-visible issues, so the default stance is to keep them off in production and enable them only where it’s safe to do so. This is why the best answer is that they should only be run in non-production instances.

ATF tests and suites are disabled by default because automated tests can affect live users and production data if they run there. They’re designed to be executed in non-production environments—like development or testing environments—where you have control over the data, states, and timing of the test runs. Running ATF in production could cause unintended changes, performance impacts, or user-visible issues, so the default stance is to keep them off in production and enable them only where it’s safe to do so. This is why the best answer is that they should only be run in non-production instances.