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

Tests for docs being up-to-date should not be part of functional tests #47

Open
ulif opened this issue Feb 26, 2018 · 1 comment
Open
Labels

Comments

@ulif
Copy link
Owner

ulif commented Feb 26, 2018

Currently we test with py.test whether headers and docs reflect the current year/month.

When a year/month marker in docs or source headers outdates, then this is a problem for packagers and release maintainers. It is not a problem for people running the code.

We might therefore do this kind of checks with tox, but in a different manner.

@ulif ulif added the bug label Feb 27, 2018
@ulif
Copy link
Owner Author

ulif commented Feb 27, 2018

Further findings: the mentioned tests fail automatically after a year (or shorter). They should fail only, if there were any commits after the year mentioned in docs and version info.

@ulif ulif mentioned this issue Feb 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant