Re: How does it work?
On Thu, 13 May 2004, Mati wrote: > > hi, > > I was wondering if there are some tools that you use to test squid? At my day job we have a functionality/compliance tool called Co-Advisor. We would be happy to give you access to the on-line version so you can test your features. In order to use the on-line version you would have to set up your Squid with public IP address. Let me know... Duane W.
Re: How does it work?
> > The second reason is that to test our code we developed a tool > > for testing squids behaviour and wonder if you would want to use it. > > Very interesting. Please eloberate on the capabilities of this tool. The tool consists of a few perl/bash scripts, so it's not too sophisticated. It tests squid's interactions with clients and servers (i.e. messages squid sends). A single test goes like this: - a predefined request is send to squid - dedicated server listens for squid's reaction - the server logs squid's request and replies with predefined response - the client receives squid's response and logs it - squid's request and response are compared to expected request and response to verify if squid behaved correctly Currently the comparison tries to match each line of the expected response/request file with squid's actual response/request. There are two options of this "line matching": - the first when verification succeeds when the line matches any line i actual squid's reponse/request, - the second when verification fails when the line matches any line i actual squid's reponse/request This allows tests to verify if squid sends proper headers, as well as if squid doesn't send improper headers... Besides the logging server and client the tool includes some scripts to automatize the testing. The first draft of the description of the tool and the scripts themselves can be found at our page: http://rainbow.mimuw.edu.pl/~ms189442/mmsquid/mmsquid.php?menu[0]=presentati ons&menu[1]=squid&menu[2]=testtools&lang=en I will have this page updated till the end of the next week so the link above won't point to "a draft of description" but to the full-featured description. Any comments are welcomed :) Regards, Mati.
Re: How does it work?
On Thu, 13 May 2004, Mati wrote: > I was wondering if there are some tools that you use to test squid? web-polygraph is quite good, but it focuses on performance not advanced functionality. > The first being that we are finishing with ETag+Vary support and want to be > sure that we haven't messed any existing functionalities up... > > The second reason is that to test our code we developed a tool > for testing squids behaviour and wonder if you would want to use it. Very interesting. Please eloberate on the capabilities of this tool. We really need something useful to build a functional test suite for Squid for the very exact same reasons you outline. > I also wondered how the code is merged to HEAD? By the developer asking to have the code merged into HEAD. There is then a short public review of the implementation and if deemed suitable it usually gets merged after a few interactions like "why have you done this this way? Isn't it better to do it like this?" or "please change this part because ..." The earlier you involve others in your developments the faster the final review process is. But we do request that a feature is reasonably finished and tested before merged. There is also some minor things complicating matters such as HEAD currently being in feature freeze to allow for Squid-3.0 to stabilize, but this (the feature freeze) is not something you have to worry about. > I mean how the decision whether to include new code or not is made... Mostly by discussion here on squid-dev. All that is needed is to get one of the core developers convinced that your solution is good, and none of the other strongly oppose inclusion. Regards Henrik
How does it work?
hi, I was wondering if there are some tools that you use to test squid? I'm asking for two reasons... The first being that we are finishing with ETag+Vary support and want to be sure that we haven't messed any existing functionalities up... The second reason is that to test our code we developed a tool for testing squids behaviour and wonder if you would want to use it. Ok... enough about testing... I also wondered how the code is merged to HEAD? I mean how the decision whether to include new code or not is made... regards, Mati.
