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

Page content #26

Open
dogweather opened this issue Feb 13, 2016 · 0 comments
Open

Page content #26

dogweather opened this issue Feb 13, 2016 · 0 comments

Comments

@dogweather
Copy link
Owner

I.e., Capybara matchers. Here's one use-case: Tests to verify that certain searches work as expected. It'd be extremely useful for webmasters of sites which have a built-in search function. At L&C College, this was something we routinely needed to make sure continued working as expected.

Maybe this will be as "simple" as implementing a matcher mirroring Capybara's have_content.

Example: Missing gitlab search result

Here's a bug I just reported for GitLab showing that the search engine results have a problem. They'd benefit from a monitor that'd tell them immediately when search for something important like this stops working:

screen shot 2016-02-13 at 1 05 28 pm

@dogweather dogweather changed the title Plan matchers for page content Page content Feb 13, 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