Is there a way to know what the ZUUL_PORT is from the tests? #139
Comments
What I have done in the past if needed, is create an endpoint on my support server I think we could expose this and other zuul configs via a ZUUL global without much fuss tho so you wouldn't need to have the above hack. |
Having the current browser + version as an environement var would be very useful too. |
Thanks @defunctzombie that sounds like a good workaround. Agreed that eventually it would be nice to have that stuff available. |
@vvo what's the use case you had in mind for the browser and version? |
@rase- : if (process.env.BROWSER === 'ie8') {
test('it should work with specific ie8 fallback', function() {
});
} Let's say you have an ajax request wrapper which does use XDomainRequest on ie8 then you would But then in --local mode, this would fail badly. |
Yeah I would strongly prefer feature detection in those cases. It also makes it clearer what exactly the browser should have/should not have for that functionality to exist. |
Uhm, I don't get this: How do you fetch the
Is something such as this actually available? Or: How do I get the |
I have some tests that require some requests to be crossdomain. I am using a support server written to listen on ZUUL_PORT and that works fine. If I log the port and set my tests to use that port for the crossdomain requests after the server starts they work.
Is this exposed at all in the tests so that I don't have that manual step of getting the port number and putting it into my tests?
The text was updated successfully, but these errors were encountered: