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.

Sign up for GitHub

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

Jump to bottom

What approach should be taken for testing in this repository? #4

Open
iKevinY opened this issue Apr 9, 2015 · 1 comment
Open

What approach should be taken for testing in this repository? #4

iKevinY opened this issue Apr 9, 2015 · 1 comment

Comments

@iKevinY
Copy link
Member

iKevinY commented Apr 9, 2015

Currently, there are two tools being migrated over to this repository: pelican-themes and pelican-import. The former doesn't have any unit tests in the main Pelican repository, but the latter does. To complicate things a little further, the tests for pelican-import currently imports various functions from support.py, but that's a discussion for another issue.

Should Travis just discover and run all the test files it finds under each "tool"?
@iKevinY iKevinY mentioned this issue Apr 9, 2015
Open
3 tasks
@TC01
Copy link

TC01 commented Jul 1, 2015

That seems reasonable to me; is there a better way to do it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@TC01 @iKevinY