ATF test error: Field not editable.

[HrishabhKumar]

I've created a test case, which is running perfectly in DEV, but it's giving error in UAT.

Below is my test and all the steps involved.

If I run the test it completes successfully in DEV instance, but gives error in UAT instance. Below is the test result of the test in UAT.

Let me know what could be the cause and how to resolve this?

Thanks

[Ankur Bawiskar · Accepted solution]

@HrishabhKumar 

the error clearly says the field cannot be edited.

Seems some script etc is making that field read-only in TEST and not in DEV.

How is the behavior when you manually open the form in TEST?

Is the field editable for that user which you are using to test?

If my response helped please mark it correct along with other ones from my response so that it benefits future readers.

[HrishabhKumar]

Hi @Ankur Bawiskar 

I didn't find any logic which could make it non editable. But yes let me try to manually execute the steps using the impersonated user.

[Sardash]

@HrishabhKumar  - Please impersonate manually with the same user and check if field is editable or read only

[vignesh parthib]

Hi @HrishabhKumar 

typically occurs during an Automated Test Framework (ATF) test run or a script execution (like in a business rule, script include, or test step) when trying to update a field that is:

• Marked as read-only in the form layout or dictionary,

• Protected by UI policy or client script, or

• Not editable in the current context eg: ACL (like in a test step trying to set a field that’s not editable at that point).

To confirm if the field is editable during ATF:

• Run a manual test in the same context and try editing short_description.
• Add a test step that verifies whether the field is editable using a "Field is Editable" test step.

Thanks,

Vignesh

If my answer solves your problem, please mark it as the correct answer.