Skip to content
This repository has been archived by the owner on Apr 7, 2022. It is now read-only.

[1LP][RFR] Uncollect Server > Database tests in test_paginator_config_pages #9976

Merged
merged 1 commit into from
Mar 13, 2020
Merged

[1LP][RFR] Uncollect Server > Database tests in test_paginator_config_pages #9976

merged 1 commit into from
Mar 13, 2020

Conversation

tpapaioa
Copy link
Contributor

Uncollect Server > Database tests in test_paginator_config_pages for 5.11 and later.

These pages in the web UI have been disabled in 5.11:

Bug 1767645 - [RFE] Hide the Configuration -> Database screen
https://bugzilla.redhat.com/show_bug.cgi?id=1767645

{{ pytest: -vv -k test_paginator_config_pages cfme/tests/configure/test_paginator.py }}

@dajoRH
Copy link
Contributor

dajoRH commented Mar 10, 2020

I detected some fixture changes in commit 11db730

The local fixture schedule is used in the following files:

  • cfme/tests/configure/test_paginator.py
    • test_paginator_details_page

Please, consider creating a PRT run to make sure your fixture changes do not break existing usage 😃

@tpapaioa tpapaioa changed the title [WIPTEST] Uncollect Server > Database tests in test_paginator_config_pages [RFR] Uncollect Server > Database tests in test_paginator_config_pages Mar 10, 2020
@valaparthvi valaparthvi changed the title [RFR] Uncollect Server > Database tests in test_paginator_config_pages [1LP][RFR] Uncollect Server > Database tests in test_paginator_config_pages Mar 13, 2020
@valaparthvi valaparthvi added the test-cleanup Test removal, collection changes, re-organization label Mar 13, 2020
@mshriver mshriver self-assigned this Mar 13, 2020
@mshriver mshriver merged commit 1ee3ee3 into ManageIQ:master Mar 13, 2020
@tpapaioa tpapaioa deleted the test_paginator_config_pages_db branch March 13, 2020 14:43
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lint-ok test-cleanup Test removal, collection changes, re-organization
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants