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

block_all_robots #1

Open
dogweather opened this issue Jan 26, 2014 · 1 comment
Open

block_all_robots #1

dogweather opened this issue Jan 26, 2014 · 1 comment

Comments

@dogweather
Copy link
Owner

While a site is in development, it's common to block all robots with html meta tags and robots.txt. This test asserts that no such setting is in place. So it's a nice test that this easy-to-forget thing has been taken care of when putting an app in production. We've also seen these blocks get accidentally enabled, which is a bad thing, and hard to debug.

It will pass, however, if partial blocks are set up for certain robots or certain parts of the site, because production sites often use those.

@dogweather dogweather changed the title matcher: not_block_all_robots Matcher: not_block_all_robots Mar 26, 2014
@dogweather
Copy link
Owner Author

This could be rolled up into the be_setup_for_production matcher.

@dogweather dogweather reopened this Jan 28, 2016
@dogweather dogweather changed the title Matcher: not_block_all_robots not_block_all_robots Jan 30, 2016
@dogweather dogweather changed the title not_block_all_robots block_all_robots Feb 9, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant