removing updated value and takes default value

[amolpati30]

Added to the entities with their respective locators:

• update_variable_value: Updating the ansible variable value in the host.
• del_variable_value: Deletes the updated value, reverts to the default value.
• read_variable_value: Read the value of ansible variable in the host.

Dependent PR: SatelliteQE/robottelo#16969

[Satellite-QE]

PRT Result

Build Number: 460
Build Status: SUCCESS
PRT Comment: pytest tests/foreman/ui/test_ansible.py::TestAnsibleCfgMgmt -k test_positive_assign_ansible_role_variable_on_host --external-logging
Test Result : ========== 1 passed, 10 deselected, 24 warnings in 837.50s (0:13:57) ===========

[LadislavVasina1]

Small change requested, otherwise looks good to me. GJ @amolpati30!

[Satellite-QE]

PRT Result

Build Number: 461
Build Status: UNSTABLE
PRT Comment: pytest tests/foreman/ui/test_ansible.py::TestAnsibleCfgMgmt -k test_positive_assign_ansible_role_variable_on_host --external-logging
Test Result : ========== 1 failed, 10 deselected, 22 warnings in 800.28s (0:13:20) ===========

[Satellite-QE]

PRT Result

Build Number: 462
Build Status: SUCCESS
PRT Comment: pytest tests/foreman/ui/test_ansible.py::TestAnsibleCfgMgmt -k test_positive_assign_ansible_role_variable_on_host --external-logging
Test Result : ========== 1 passed, 10 deselected, 24 warnings in 892.06s (0:14:52) ===========

[LadislavVasina1]

ACK

[lhellebr]

Is there a reason why each of these functions isn't an atomic function? Is it important to read RIGHT AFTER updating/deleting?

[amolpati30]

@lhellebr
While working on this entity, I noticed that some features do not have a specific column for each actions item in the table. For example, actions like Submit, Cancel, and Edit point to a single column (indexed as 5). However, when we update a value and attempt to delete it, a new "3-dot" option appears, which does not correspond to any specific column, even though it is part of the table.
Due to these differences, two distinct methods are required. And I am reading the values here for assertion purposes, to verify the data after update and delete.

[lhellebr]

Let me rephrase my question. Let's take one of the functions: read_value_after_del. Why is it a single function? What is so specific about operation "delete and then read"? I would think this can be two functions: delete and read and the test can just call one after the other.

[amolpati30]

Thank you for the clarification. I would suggest that if we are deleting/updating value, we should read the value for verification/assertion purposes. I have already added this functionality in the method. However, creating a separate method specifically for reading the value is also a good idea.

This way, we could have two methods for update/delete operations and a third method to handle reading the value. Do you think I should update the implementation accordingly?

[lhellebr]

I think yes, if you don't have a specific reason to make those inherently atomic operations a single operation in this case. I think that's also the way we have it everywhere else.

[Satellite-QE]

PRT Result

Build Number: 463
Build Status: UNSTABLE
PRT Comment: pytest tests/foreman/ui/test_ansible.py::TestAnsibleCfgMgmt -k test_positive_assign_ansible_role_variable_on_host --external-logging
Test Result : ========== 1 failed, 10 deselected, 26 warnings in 769.00s (0:12:49) ===========

[amolpati30]

trigger: test-robottelo
pytest: tests/foreman/ui/test_ansible.py::TestAnsibleCfgMgmt -k test_positive_assign_ansible_role_variable_on_host
robottelo: 16969

[Satellite-QE]

PRT Result

Build Number: 464
Build Status: SUCCESS
PRT Comment: pytest tests/foreman/ui/test_ansible.py::TestAnsibleCfgMgmt -k test_positive_assign_ansible_role_variable_on_host --external-logging
Test Result : ========== 1 passed, 10 deselected, 26 warnings in 1420.64s (0:23:40) ==========

[Gauravtalreja1]

Why changing the buttons order here?
and could you add some descriptions about change to this locators in the description?

[amolpati30]

Locators 6 and 7 are not supported, and there is no column for the edit, submit, or cancel buttons. Based on the index, these buttons correspond to key 5. To enable editing, I added the edit locator under key 5. For submitting the value, I created another variable with the same key (5) but for the submit action. However, combining them does not work—I tried that as well.