Are regression/unit test suites being run on upstream sources?
WBaer at gmx.de
Sat Aug 6 09:23:28 UTC 2005
Barry Hawkins wrote:
> This has me wondering; people aren't foregoing the unit test suites
> on upstream packages during a build in order to get a package into main
> more expediently, are they? It is my hope that this is not being done.
> While unit test suites should not be considered regression tests, they
> are at least a low-cost minimal level of assurance that upstream uses to
> ensure that their artifacts are behaving as expected.
I have enabled unit tests and are more and more enabling this in future
uploads - but as always things are not only black and white.
I everytime also run the unit tests against a non-free JDK, because I
found that several unit tests in upstream packages also contain wrong
tests or tests that also fail in non-free JDKs. For this case I enable
the unit tests but don't let the build fail and also include in the
changelog an explanation which tests are ok to fail because they also
fail with the non-free JDKS.
Sometimes the debian package does not enable every feature of the
upstream package because of yet missing dependencies or license issues.
However the unit tests are sometimes designed that they cannot be run
only for the features build but are depending on everything. In this
case I only run (by hand) the correct test subset and don't enabling
the testcase in the package build.
But in general I support you on using unit tests and moving
packages only to main if the unit tests succeed the same tests as with
More information about the pkg-java-maintainers