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

Improve tests #16

Open
pathawks opened this issue Dec 23, 2016 · 5 comments
Open

Improve tests #16

pathawks opened this issue Dec 23, 2016 · 5 comments

Comments

@pathawks
Copy link
Member

I wonder if we could whip something up that runs when the site is built on CI that verifies that all Gems exist, and URLs don't 404.

Seems like it’d be as easy as adding something to _plugins/

@pathawks pathawks added the tests label Dec 23, 2016
@pathawks
Copy link
Member Author

Currently, CI will verify that no URLs 404. Should be not so difficult to do something similar for Gems.

@parkr
Copy link
Member

parkr commented Jan 16, 2017

@pathawks Before we make this the official home of all plugins & themes, let's come up with tests to enforce all the correct fields are present, etc.

@pathawks
Copy link
Member Author

I'd like to create a test that makes sure anything claiming to be a Gem is actually listed on RubyGems.org

@pathawks
Copy link
Member Author

pathawks commented Feb 2, 2017

We should exclude urls from https://github.com/jekyll/plugins/edit/master from HTML-Proofer, as pages that have not yet been added will not yet exist.

We should type check all the YAML of themes and plugins.

@jekyllbot
Copy link
Contributor

This issue has been automatically marked as stale because it has not been commented on for at least two months.

The resources of the Jekyll team are limited, and so we are asking for your help.

If this is a bug and you can still reproduce this error on the master branch, please reply with all of the information you have about it in order to keep the issue open.

If this is a feature request, please consider whether it can be accomplished in another way. If it cannot, please elaborate on why it is core to this project and why you feel more than 80% of users would find this beneficial.

This issue will automatically be closed in two months if no further activity occurs. Thank you for all your contributions.

@jekyllbot jekyllbot added the stale label Apr 2, 2017
@parkr parkr reopened this Jun 2, 2017
@parkr parkr reopened this Aug 3, 2017
@pathawks pathawks reopened this Oct 3, 2017
@pathawks pathawks added pinned and removed stale labels Oct 3, 2017
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

3 participants