Test for all hosts page manage columns

[sambible]

Problem Statement

Automation for 6.16 feature work as part of the All Hosts pt2 improvement.

Related Issues

SatelliteQE/airgun#1421 - airgun support PR

PRT

trigger: test-robottelo
pytest: tests/foreman/ui/test_host.py -k 'test_all_hosts_manage_columns'
airgun: 1421

[Satellite-QE]

PRT Result

Build Number: 7337
Build Status: UNSTABLE
PRT Comment: pytest tests/foreman/ui/test_host.py -k test_all_hosts_manage_columns --external-logging
Test Result : ========== 1 failed, 50 deselected, 60 warnings in 806.67s (0:13:26) ===========

[sambible]

trigger: test-robottelo
pytest: tests/foreman/ui/test_host.py -k 'test_all_hosts_manage_columns'
airgun: 1421

[Satellite-QE]

PRT Result

Build Number: 7339
Build Status: UNSTABLE
PRT Comment: pytest tests/foreman/ui/test_host.py -k test_all_hosts_manage_columns --external-logging
Test Result : ========== 1 failed, 50 deselected, 60 warnings in 818.58s (0:13:38) ===========

[sambible]

trigger: test-robottelo
pytest: tests/foreman/ui/test_host.py -k 'test_all_hosts_manage_columns'
airgun: 1421

[Satellite-QE]

PRT Result

Build Number: 7340
Build Status: SUCCESS
PRT Comment: pytest tests/foreman/ui/test_host.py -k test_all_hosts_manage_columns --external-logging
Test Result : ========== 1 passed, 50 deselected, 60 warnings in 835.34s (0:13:55) ===========

[pondrejk]

some clarifications needed

[lhellebr]

Indeed, it seems like the first part of this PR is a duplicate and the second was added by mistake and should be part of another PR.

[sambible]

I'll comment down here as well for additional visibility: This work, like other PRs around this All Hosts area, is to provide coverage for the currently in development "All Hosts" page. For those not familiar with the area, this will combine functionality from the existing Hosts page, and Content Hosts pages.

Manage columns is a feature on this page, and on the Host page. Until the original Host page is retired completely, coverage for these two different areas will need to exist side by side, and in some cases, should and will look similar.

[lhellebr]

Would it be better to have a single test, parametrized to use different Airgun entities, one for Hosts and one for All Hosts? Just a question, non-blocking.

[vsedmik]

Looks good! Just a couple of nitpicks left.

[sambible]

Would it be better to have a single test, parametrized to use different Airgun entities, one for Hosts and one for All Hosts? Just a question, non-blocking.

This would be a more elegant solution, yes. The cases where the two tests look this similar though, are not that common. Seems worth investigating, though. (outside this PR)