There's a lot of ugly solutions out there regarding this problem and rightfully so, it's a pain in the ass. I've gone through a good number of options and found the following to be the most simple. Warning: It only works on Mac OS X.
Capybara allows you to set the server port to run the test server on. This may or may not be necessary depending on your environment. It was necessary for me because Pow hijacks my default port.
Capybara.server_port = 6543
Mac OS X comes with a handy *.127localhost.com domain configured for you. So you can do contact.127localhost.com, test.127localhost.com, etc and it will all point to 127.0.0.1.
When you need to use your subdomain, simply use a url helper:
describe 'as a guest user on the mobile login page' do
visit login_url(:subdomain => 'contact', :host => '127localhost.com', :port => 6543)
it 'shows me the login form' do
Fenangling the /etc/hosts feels dirty and pollutes domain resolution.
Ultimately, it would be awesome to boot a Pow server for testing and use something like http://contact.myapp.test where the development app lives at http://contact.myapp.dev. It's possible to get Pow to boot at http://myapp.test by using the POW_DOMAINS environment variable. The issue here is the Pow server still runs in development. You can start the Pow server in an environment other than development by using .powenv. The issue here is managing the .powenv file so that it only exists during testing. Also, there would be additional boot time by restarting the Pow server.
I hope that in future versions of Pow, it's possible to configure the environment based on the top-level domain such as dev or test. That way, you can modify /etc/resolver/test to point to the port for which your test app lives during runtime. The resolver files are pretty simple and could be modified to look like the following:
# Lovingly generated by Pow
Until Pow provides the ability to run different environments, I'll stick to *.127localhost.com.
Posted by Mike Pack on 09/16/2011 at 11:01AM