Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixes #35817 - Avoid using fixtures for test settings #9530

Closed
wants to merge 1 commit into from

Conversation

ekohl
Copy link
Member

@ekohl ekohl commented Dec 2, 2022

When running rake snapshots:generate it doesn't load the fixtures. This normally happens in the test setup code, but snapshot generation doesn't use this. This patch uses the settings DSL to set a different default depending on the environment. An additional benefit is that the code is more localized.

When running rake snapshots:generate it doesn't load the fixtures. This
normally happens in the test setup code, but snapshot generation doesn't
use this. This patch uses the settings DSL to set a different default
depending on the environment. An additional benefit is that the code is
more localized.
@theforeman-bot
Copy link
Member

Issues: #35817

@ezr-ondrej
Copy link
Member

ezr-ondrej commented Dec 3, 2022

Both of the failures are about the setting table being empty IMHO.
One of them easily fixable by just creating the setting tho I'm not sure how to fix the uniqueness test.

@ezr-ondrej
Copy link
Member

This mixes test code with production code, which I'm generally against, but the benefits you're describing are outweighing the cons here so 👍

@stejskalleos stejskalleos self-assigned this Dec 13, 2022
Copy link
Contributor

@stejskalleos stejskalleos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like failures are related to the changes.

@theforeman-bot
Copy link
Member

Thank you for your contribution, @ekohl! This PR has been inactive for 3 months, closing for now.
Feel free to reopen when you return to it. This is an automated process.

@stejskalleos
Copy link
Contributor

Reopening the PR, I'm still having the problem on the develop branch.
@ekohl can you please rebase the PR?

@github-actions github-actions bot removed the Inactive label Feb 27, 2024
@jcpunk
Copy link
Contributor

jcpunk commented Mar 26, 2024

I think I've got work blocked waiting for this PR

@github-actions github-actions bot added the Stale label Jun 25, 2024
Copy link

github-actions bot commented Jul 2, 2024

Thank you for your contribution! This PR has been inactive for 3 months, closing for now. Feel free to reopen when you return to it. This is an automated process.

@github-actions github-actions bot closed this Jul 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
5 participants