Same issue is true for a lot of QA tests too ... - some tests assume certain hostnames to be on the network - some tests assume a Kerberos infrastructure to be in place on the network ...
To your question, we could maybe use an existing piece of code to run a proxy server inside a test? I haven't looked into that tho. Best JC 2009/5/8 Peter Firmstone (JIRA) <[email protected]> > Create proxy server implementation for jtreg test of > net/jini/jeri/http/echo/EchoImpl.java > > ------------------------------------------------------------------------------------------ > > Key: RIVER-306 > URL: https://issues.apache.org/jira/browse/RIVER-306 > Project: River > Issue Type: Sub-task > Components: Web site and infrastructure > Environment: jtreg tests > Reporter: Peter Firmstone > > > From Peter Jones comment: > > FAILED: net/jini/jeri/http/echo/EchoImpl.java > > This test failed for me because it couldn't resolve the host name > "jiniproxy", where-- for one variation of the test-- it is expecting to > find an HTTP proxy, in order to test HTTP proxy support for the > net.jini.jeri.http transport implementation. Clearly, this was an > assumption about the internal Sun environment which doesn't even hold > here/there anymore. > > How can we handle this? > > Can we simulate the proxy server, if so how? > > Do we write our own lightweight java proxy server, and implement it > locally, upload the class files to a reserved area on apache and download > them back through the local proxy server? Or is there a way to host the > proxy server and web server locally somehow without port conflicts, how do > we simulate the conditions that occur? > > Your thoughts please. > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online. > >
