In practical software test automation projects, which of the following is a common problem or challenge that teams frequently face?

Introduction / Context:
Test automation is widely adopted to improve regression testing speed, repeatability, and coverage. However, automation is not a magic fix and introduces its own challenges. Teams that start automation initiatives often discover that building and maintaining automated tests can be difficult, especially as the system under test evolves. This question asks which stated problem is realistic and commonly encountered in automation projects.

Given Data / Assumptions:
- Automation is applied to applications with user interfaces, APIs, or other externally visible behaviour.
- Requirements, workflows, and user interfaces may change over time as the product evolves.
- The options describe different claims about automation projects, some accurate and some exaggerated or false.

Concept / Approach:
Automated tests are software assets that need maintenance just like the application code. When the user interface changes, element locators, workflows, and test data may all need to be updated. Requirements shifts can also invalidate or modify existing tests. Therefore, maintenance cost is a real and common problem. In contrast, it is unrealistic to say that automation tools never require programming skills, that manual testing is no longer needed, or that automation is always cheaper and faster from day one. These claims overlook the significant initial investment and the ongoing cost of maintaining test suites.

Step-by-Step Solution:
1. Consider option A: in many projects, UI automation scripts break when layout, element identifiers, or flows change. Testers must then update locators, assertions, and data, which can be time consuming. 2. This maintenance burden is especially high in agile projects with frequent releases or in early stages of design when the UI is not stable. 3. Option B claims that automation tools never require programming skills. In reality, even tools with record and playback modes benefit from scripting and logic, so this statement is not accurate. 4. Option C suggests that manual testing is eliminated after automation is introduced, but exploratory testing and usability checks still require human judgement. 5. Option D asserts that automation is always cheaper and faster from day one, ignoring the initial investment needed to build the framework and tests. 6. Therefore, option A is the realistic and commonly observed challenge among the choices.

Verification / Alternative check:
Industry experience and case studies show that many teams struggle with brittle automated UI tests, especially when locators are tightly coupled to specific HTML attributes or when underlying workflows change often. Automation best practices such as using stable identifiers, page object patterns, and API level tests exist precisely to reduce this maintenance cost. The presence of these mitigation techniques in literature and tooling confirms that maintenance of automation assets is a recognised and serious concern.

Why Other Options Are Wrong:
Option B is wrong because even so called scriptless tools eventually require custom logic, conditions, and integration, which benefit from programming knowledge. Option C is incorrect since manual testing remains necessary for exploratory, usability, compatibility, and acceptance testing. Option D is misleading because automation requires an upfront investment, and cost savings are only realised over time as the automated tests are reused. These options describe myths or oversimplifications, not common problems. Only option A captures a real and frequent challenge: high maintenance effort when the UI or requirements change often.

Common Pitfalls:
Teams sometimes underestimate maintenance effort and over promise the benefits of automation to management. They may automate unstable areas of the application first, causing scripts to break with every release. Another pitfall is neglecting good design practices for test code, leading to duplicated logic and hard coded locators that are hard to maintain. Understanding that automation is a long term investment and planning for maintenance from the beginning helps avoid disappointment and ensures sustainable benefits.

Final Answer:
A realistic and common challenge in test automation projects is high maintenance effort when the user interface or requirements change frequently.