Skip to content

What does it mean to test a package contribution? #2

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

Open
vsoch opened this issue Jan 2, 2019 · 0 comments
Open

What does it mean to test a package contribution? #2

vsoch opened this issue Jan 2, 2019 · 0 comments

Comments

@vsoch
Copy link
Contributor

vsoch commented Jan 2, 2019

When a user (or developer) contributes a package, it needs to be tested before being added to the Penrose Package Library. Testing should ensure that some list of criteria of goodness, and completeness are met. What are these criteria? Here are some general points to get thinking started:

  • Looking for Github pages to be turned on (exposing metadata)
  • Some number of examples provided
  • Retrieving the file and testing to confirm produces a working diagram with the example.

Ideally, we would want examples to be rendered somewhere. If the testing happens here, we could easily retrieve (and render) and deploy examples on Github pages here. It might be better done on the package Github pages too.

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

No branches or pull requests

1 participant