Include the test suite in releases (and make it test the new release)
Bug #1880696 reported by
Michael Orlitzky
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| SPF Engine |
Triaged
|
Wishlist
|
Unassigned | ||
Bug Description
When installing spf-engine on Gentoo, we'd like to be able to run the test suite on the newly "built" version before the install phase overwrites the old version. That helps our users when there's a bug that the maintainer doesn't know about, and helps the maintainer when it's time to say e.g. "this package works with python-3.9".
I know it would be annoying and would involve reworking the whole test suite, but my feature request is that the test suite be included in the releases, and be modified to test the new release instead of the installed version. I have to imagine that would be nicer for you as well, since you wouldn't have to run the installation routine before running the test suite?
Revision history for this message
| Scott Kitterman (kitterman) wrote | #1 |
| Changed in spf-engine: | |
| importance: | Undecided → Wishlist |
| milestone: | none → spf-engine-future |
| status: | New → Triaged |
To post a comment you must log in.
Yes, that all makes sense. I'd like to be able to run the test suite in Debian too. It would require something other than the pile of python I have now, so probably no time soon. If someone cares to work on it, I'd be glad to discuss.