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

don't show abusive projects in the public gallery #15566

Merged
merged 1 commit into from Jun 2, 2017

Conversation

davidsbailey
Copy link
Member

verified manually that projects marked as abusive can be "published" but then don't show up in the public gallery

@Bjvanminnen
Copy link
Contributor

Can/should we write tests for this?

@davidsbailey
Copy link
Member Author

we don't actually have any test coverage of the DB query itself -- in unit tests we are stubbing the value of the dataset that is returned. It looks theoretically possible to unit test the query code via Sequel-Fixture.

We could also do a UI test to get end-to-end coverage for the abuse case in particular. These would be complicated slightly because we cache the public gallery data fetch for 1 minute.

@davidsbailey
Copy link
Member Author

Do either of these seem worth pursuing as part of this PR?

@Bjvanminnen
Copy link
Contributor

Your call. If it seems super difficult, perhaps not.

@davidsbailey davidsbailey merged commit 1a2143b into staging Jun 2, 2017
@davidsbailey davidsbailey deleted the filter-abusive-published-projects branch June 2, 2017 18:05
@davidsbailey
Copy link
Member Author

Merging this now since it seems urgent, and testing it properly by either means seems like a half to whole day endeavor. I will make a note to cover this case when we add UI tests for this feature.

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

Successfully merging this pull request may close these issues.

None yet

2 participants