apt/test/integration/test-apt-helper, branch 1.2.6Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=1.2.62015-12-19T22:04:34Ztests: support spaces in path and TMPDIR2015-12-19T22:04:34ZDavid Kalnischkiesdavid@kalnischkies.de2015-12-15T16:20:26Zurn:sha1:3abb6a6a1e485b3bc899b64b0a1b7dc2db25a9c2
This doesn't allow all tests to run cleanly, but it at least allows to
write tests which could run successfully in such environments.
Git-Dch: Ignore
tests: use quiet level 0 by default in tests2015-11-19T16:13:56ZDavid Kalnischkiesdavid@kalnischkies.de2015-11-19T15:00:33Zurn:sha1:87d6947d51717e8b0e975d913986161598a7259a
Git-Dch: Ignore
tests: don't use hardcoded port for http and https2015-09-15T08:16:09ZDavid Kalnischkiesdavid@kalnischkies.de2015-09-14T22:33:12Zurn:sha1:6c0765c096ffb4df14169236c865bbb2b10974ae
This allows running tests in parallel.
Git-Dch: Ignore
various changes to increase test-coverage2015-09-14T13:22:19ZDavid Kalnischkiesdavid@kalnischkies.de2015-09-12T08:35:49Zurn:sha1:7414af7fa88164209eec9c585b8d175c1618ecbc
And of course, testing obscure things ends up showing obscure 'bugs' or
better shortcomings/inconsitencies, so lets fix them with the tests.
Git-Dch: Ignore
use unusable-for-security hashes for integrity checks2015-09-01T12:19:44ZDavid Kalnischkiesdavid@kalnischkies.de2015-09-01T11:58:00Zurn:sha1:63d609985eb7eefa5f2332bfe4fab96f017760a1
We want to declare some hashes as not enough for security, so that a
user will need --allow-unauthenticated or similar to get data secured
only by those hashes, but we can still us these hashes for integrity
checks if we got them.
Consider md5sum no longer a usable hash2015-09-01T09:29:49ZMichael Vogtmvo@ubuntu.com2015-09-01T09:13:48Zurn:sha1:55ae7a516126f9f064d8353bf962256b7307590a
The md5sum hash is broken since some time and we should no longer
consider it a usable hash. Also update the tests to reflect this.
fix download-file using testcases to run as root2015-06-09T10:57:36ZDavid Kalnischkiesdavid@kalnischkies.de2015-06-07T07:35:37Zurn:sha1:fec55559451dc1c440c4770ee3faa116522fc59c
Git-Dch: Ignore
test exitcode as well as string equality2015-03-16T17:01:54ZDavid Kalnischkiesdavid@kalnischkies.de2015-03-09T23:59:44Zurn:sha1:25b86db159fbc3c043628e285c0c1ef24dec2c6e
We use test{success,failure} now all over the place in the framework, so
its only consequencial to do this in the situations in which we test for
a specific output as well.
Git-Dch: Ignore
merge debian/sid into debian/experimental2015-03-16T16:59:31ZDavid Kalnischkiesdavid@kalnischkies.de2015-03-09T00:34:10Zurn:sha1:d61960d9244340956a27f4ca46aecd15cc75e18bdispose http(s) 416 error page as non-content2014-12-22T13:23:39ZDavid Kalnischkiesdavid@kalnischkies.de2014-11-29T16:59:52Zurn:sha1:92e8c1ff287ab829de825e00cdf94744e699ff97
Real webservers (like apache) actually send an error page with a 416
response, but our client didn't expect it leaving the page on the socket
to be parsed as response for the next request (http) or as file content
(https), which isn't what we want at all… Symptom is a "Bad header line"
as html usually doesn't parse that well to an http-header.
This manifests itself e.g. if we have a complete file (or larger) in
partial/ which isn't discarded by If-Range as the server doesn't support
it (or it is just newer, think: mirror rotation).
It is a sort-of regression of 78c72d0ce22e00b194251445aae306df357d5c1a,
which removed the filesize - 1 trick, but this had its own problems…
To properly test this our webserver gains the ability to reply with
transfer-encoding: chunked as most real webservers will use it to send
the dynamically generated error pages.
(The tests and their binary helpers had to be slightly modified to
apply, but the patch to fix the issue itself is unchanged.)
Closes: 768797