On Mon, 18 Jul 2016 17:52:18 +0200 =?utf-8?q?Santiago_Ruano_Rinc=C3=B3n?= wrote: > > Please, find attached an updated debian/tests dir. I have updated > Ubuntu's current files and modified some Ubuntu specificities. > > Amos, these tests are independent from squid building process. Instead, > they make it possible to automatically test squid on a running > environment. The declared dependencies relate only to the testbed > environment.
Thanks for the update. Yes, I know they are supposed to be testing an emulation of production systems. Its just that they don't do it well/right. The issues I have was/is that they used to be far less well documented (that seems to be better now), and many of the tests are testing things which are impossible for Debian builds to pass. The prominent TODO list entries (still) are going on about how to test squidGuard package in isolation - without using Squid or any of the other test environment dependencies, that at least should be moved to squidguard package auto-tests. Specific examples for anyone with time and interest in fixing them; - HTTPS proxy service on a proxy built without (OpenSSL) HTTPS support, - Apparmour integration tests for a proxy not packaged with any AppArmour integration, - Upstart configuration and testing for a package without Upstart integration. Fine for Ubuntu who build packages with those integrations, but if the tests actually work they are guaranteed to fail on Debian packages which don't. I'm surprised that the HTTPS tests would even work on the Ubuntu packages they were designed for, which do not have OpenSSL support either. And when these tests were submitted squidclient did not have any GnuTLS support. So those tests make some sense now (except not going through the main proxy), but only since Aug 2015 - not way back in 2013. Cheers Amos
