alvaro at octality
Nov 27, 2009, 7:23 AM
Post #1 of 1
(217 views)
Permalink
|
|
For the record: Running the QA bench through a proxy
|
|
Hello there,
Did you guys know that the full QA bench can be run through a Cherokee proxy server? This is something I implemented a few months ago in order to test the just born handler_proxy module.
The idea is pretty simple, and the process straightforward. We tell the QA bench to run thru a proxy located in localhost:2222, for instance. We also tell it to stop until we hit enter (-d1):
==============
cd qa
./run-tests.py -Plocalhost:2222 -d1
==============
As you'll see, it will generate a configuration file for us to launch the proxy server:
==============
Server
PID: 29909
Path: ../cherokee/cherokee-worker
Mods: ../cherokee/.libs/
Deps: ../cherokee/
Panic: ../cherokee/cherokee-panic
Proxy conf: /tmp/tmprV6k4Hcherokee_proxy_cfg
==============
at this point, we only have to open a new terminal, launch the Cherokee proxy server and hit enter to unlock tester side of the QA bench:
==============
cherokee -C /tmp/tmprV6k4Hcherokee_proxy_cfg
==============
Almost every single QA test will be perform through the proxy server. There are a few exceptions though. Tests involving the X-Real-IP header will be skipped, for example. It is not a big deal anyway, those are around 5 o 6 test out of almost 250.
Cheers!
--
Octality
http://www.octality.com/
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev
|
