RE: Release testing questions
I see, thank you very much for the explanation Paul. Sorry I sent it to the wrong mailing list.
> -----Original Message-----
> From: Paul Wise <pabs@debian.org>
> Sent: Wednesday, June 8, 2022 9:52 AM
> To: debian-riscv <debian-riscv@lists.debian.org>
> Subject: Re: Release testing questions
>
> On Tue, 2022-06-07 at 13:53 +0000, Tienhock Loh wrote:
>
> > I don’t see many details about how Debian runs test (automated or
> manual).
> > Is autopkgtest “the test” that Debian Developer/Maintainer use to
> > ensure that the packages that is updated is healthy?
>
> There are several testing situations that happen:
>
> The maintainer will often manually test that the package still works by using it
> before they upload new versions.
>
> The people who use Debian testing, unstable and or experimental will use
> packages and report any problems that they notice to Debian or upstream,
> maybe via bug reports or maybe via support requests.
>
> https://www.debian.org/Bugs/Reporting
>
> The package build will often run the automated tests provided by upstream,
> the dh_auto_test script from debhelper automatically detects these and
> runs them. The Debian maintainer may also add additional build-time tests,
> but that doesn't happen often. The package builds happen when the
> package is updated, but we have several efforts to rebuild every package on
> a regular basis to check these tests.
>
> https://manpages.debian.org/dh_auto_test
>
> The piuparts package and service tests that each already built binary package
> can be installed and removed safely. Currently the service is only testing
> amd64/i386 because the code doesn't support additional architectures. The
> package should be possible to run anywhere though.
>
> https://piuparts.debian.org/
>
> The autopkgtest package and debci service installs each already built binary
> package and runs tests defined by the Debian maintainer that aim to ensure
> that the binary we ship actually works. Often these will run the upstream
> build-time tests using the binary package. Sometimes upstream themselves
> have as-installed testing that can be used.
>
> https://ci.debian.net/doc/
> https://salsa.debian.org/ci-
> team/autopkgtest/raw/master/doc/README.package-tests.rst
>
> There are a lot of other Debian QA efforts too, see this page:
>
> https://wiki.debian.org/qa.debian.org
>
> PS: this isn't really the right list for this question, since it isn't specific to RISC-
> V, the debian-mentors list would be more appropriate, that list aims to help
> new contributors find their way in Debian.
>
> --
> bye,
> pabs
>
> https://wiki.debian.org/PaulWise
Reply to: