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 #32029 - test coverage for taxed_and_untaxed #8370

Merged
merged 2 commits into from
Mar 9, 2021

Conversation

ezr-ondrej
Copy link
Member

@ezr-ondrej ezr-ondrej commented Mar 7, 2021

Adding test coverage for taxed_and_untaxed scope so we have better confidency over its refactorings.

Note I've splitted to two commits, so the additions are more readable.
So for easier review just take a look at the last commit.

Add scoping for current search tests to divide those and newly added tax
and permission tests.
@theforeman-bot
Copy link
Member

Issues: #32029

@ezr-ondrej ezr-ondrej changed the title Fixes #32029 - test coverage for taxed_and_untaxed [WIP] Fixes #32029 - test coverage for taxed_and_untaxed Mar 7, 2021
@ezr-ondrej ezr-ondrej force-pushed the audit_tests branch 3 times, most recently from bcb7204 to afa0135 Compare March 7, 2021 17:50
@ezr-ondrej ezr-ondrej changed the title [WIP] Fixes #32029 - test coverage for taxed_and_untaxed Fixes #32029 - test coverage for taxed_and_untaxed Mar 7, 2021
@tbrisker
Copy link
Member

tbrisker commented Mar 8, 2021

One of the unit tests failed, and integration tests stalled so there is probably something wrong here

@ezr-ondrej
Copy link
Member Author

integration tests stalled so there is probably something wrong here

It seems to be my simple code improvement fault. I've removed it, it didn't belong here. We are green, but testing the bugged version. (current subtaxonomy allows to see parent records).
But I believe this is not the place to fix it.

Copy link
Member

@tbrisker tbrisker left a comment

Choose a reason for hiding this comment

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

Can you please open an issue to fix the wrong behavior?

@ezr-ondrej
Copy link
Member Author

I've created two, because two is more than one! https://projects.theforeman.org/issues/32053

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants