diff options
Diffstat (limited to 'zarb-ml/mageia-dev/attachments/20130110/bfa4f619/attachment.html')
| -rw-r--r-- | zarb-ml/mageia-dev/attachments/20130110/bfa4f619/attachment.html | 31 |
1 files changed, 31 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/attachments/20130110/bfa4f619/attachment.html b/zarb-ml/mageia-dev/attachments/20130110/bfa4f619/attachment.html new file mode 100644 index 000000000..bafeb735f --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20130110/bfa4f619/attachment.html @@ -0,0 +1,31 @@ +<div dir="ltr">Thanks Guillame. I wasn't aware of this and did not manage to find that in the wiki. I thought the only tests performed where RPM lint checks, manual checks by the QA and some undefined checks by the maintainers.<div> +<br></div><div>Anyhow, I assume the 'make test' is performed on the build server. Your experiences might prove me wrong, but wouldn't it be better to perform tests on a different installation?<br></div></div><div class="gmail_extra"> +<br><br><div class="gmail_quote">2013/1/4 Guillaume Rousse <span dir="ltr"><<a href="mailto:guillomovitch@gmail.com" target="_blank">guillomovitch@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> +Le 04/01/2013 10:15, Jochen Breuer a écrit :<br> +<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> +<br> +<br> +2013/1/4 Guillaume Rousse <<a href="mailto:guillomovitch@gmail.com" target="_blank">guillomovitch@gmail.com</a><br> +<mailto:<a href="mailto:guillomovitch@gmail.com" target="_blank">guillomovitch@gmail.<u></u>com</a>>><div><div class="h5"><br> +<br> + We already run existing tests suite during package build... Running<br> + them again on a different host would just change the execution<br> + environment to use runtime dependencies instead of build time<br> + dependencies. I don't know if the potential results are worth the<br> + additional infrastructure needed.<br> +<br> +<br> +I was under the impression, that only some kind of lint checking of the<br> +RPM was performed. I'm talking about checking the functionality of the<br> +packaged software. Are you already doing that? What kind of tests are<br> +performed during packaging?<br> +</div></div></blockquote> +Running 'make check', or 'make test', or any other software test suite. Just check for %check section in package spec file, for instance:<br> +<a href="http://svnweb.mageia.org/packages/cauldron/python/current/SPECS/python.spec?revision=278990&view=markup" target="_blank">http://svnweb.mageia.org/<u></u>packages/cauldron/python/<u></u>current/SPECS/python.spec?<u></u>revision=278990&view=markup</a><span class="HOEnZb"><font color="#888888"><br> + +<br> +-- <br> +BOFH excuse #66:<br> +<br> +bit bucket overflow<br> +</font></span></blockquote></div><br></div> |