Bromine Blog
Previous
May 16, 2008 7:10 AM
Bromine
in response to: Andras Hatvani
Bromine
in response to: Andras Hatvani
Could you rephrase your question?
May 16, 2008 7:24 AM
Andras Hatvani
in response to: Bromine
Andras Hatvani
in response to: Bromine
In my company we use Selenium Chrome provided by the IDE. The test cases, test suites and selenium are stored on a dedicated test automation server, where we can modify anything we like.
Is it possible with Bromine to maintain and manage files on external resources like in this case?
May 16, 2008 8:23 AM
Bromine
in response to: Andras Hatvani
Bromine
in response to: Andras Hatvani
Chrome is a special kind of the firefox browser that allows cross site scripting. Maybe you meant selenium core?
I fail to understand how the IDE can provide this?
But, to answer your question:
Bromine works with selenium core as well as selenium RC.
The RC tests have to be stored on the server running Bromine.
The core tests have to be stored on the site that is tested.
I'm sorry for the poor answer. Explain in depth what you'd like and make sure to get all the terms correct. Otherwise it quickly gets confusing
May 27, 2008 3:38 PM
Tim Alexander
in response to: Bromine
Tim Alexander
in response to: Bromine
Let me have a shot.
First, I believe I know your issue Andras, and others likely have it too. It has to do with the Cross Site Scripting protection in most browsers. Essentially, you can't test a site on any server other than the selenium server. If this is the case, I have a bit of a fix. I originally wrote it for Selenium Test Manager (a kind of bromine substitute that I wrote myself some time back)
I have a Weblogic Server that I need to test applications on. Of course, that doesn't run PHP naturally, and it wouldn't be a good test if there were extensive modifications. So, I've used a Reverse Proxy in Apache to trick the browser into testing it even though there's security in place to prevent cross site scripting.
Essentially, you setup Apache on a server, and install selenium core on it in a selenium subdirectory. Then, install the mod-proxy module. (there are guides out there for this).
Insert the following lines into the virtual host, replacing as needed. Here, we're just setting up a reverse proxy to the server running the actual website we want to test, in this case a site called myprog on linux10 port 7000
ProxyPass /myprog http://linux10:7000/myprog
ProxyPassReverse /myprog http://linux10:7000/myprog
Restart apache, and you should be able to go to your apache server at /myprog and it will work. Make sure that your website is in a subdirectory and not on the root of the webserver under test. Otherwise, this will fail, as it needs a basic folder structure that it can cope with.
Jun 2, 2008 6:46 AM
faisal
faisal
Hi Bromine
when can we accept a completed version, i have installed it but i don't feel to use it.
Jun 2, 2008 5:27 PM
Andras Hatvani
in response to: Tim Alexander
Andras Hatvani
in response to: Tim Alexander
Hi Tim,
thanks for your response. The current project we're working on has redirects to other domains, also to SSL-secured ones, so a proxy couldn't forward those requests.
But since we also have to execute browser compatibility tests using SIDE/Chrome is only a half solution...
Andras
Jun 3, 2008 9:13 AM
Tim Alexander
in response to: Andras Hatvani
Tim Alexander
in response to: Andras Hatvani
Then most likely your solution is going to be SeleniumRC. That will allow you to store central cases in bromine, and then execute them on boxes running the various browsers.
I was fairly opposed to it at first because it was a bit more difficulf for my testers to use than Selenium Core, and i couldn't see all the inner workings as well as I can with Core. But I used it with Bromine recently and I have to say I'm impressed. It's just as easy as Selenium Core is, it's just distributed computing (you can use 1 computer if you're hosting Selenium on a box that has a browser though I believe).
It's not going to be as easy as plugging in a chrome URL from the IDE to test against. Most of the browsers have some serious protection for exactly that reason (so that people can't mess with your browser that way). In general, the only way to archive all tests on a central server, and execute them without running into XSS issues (as far as I know) is to use Selenium RC, or Selenium Grid.
I know you said that you didn't want to use Selenium RC, but could you please explain why? This will help figure out what technology is right for you, and if we can build something into Bromine in the future to help enable you to use it in the way that you need.
Jun 4, 2008 5:58 AM
Andras Hatvani
in response to: Tim Alexander
Andras Hatvani
in response to: Tim Alexander
I tried RC one and a half year ago and it was disappointing at that time due to no/not working experimental support for SSL. Furthermore, at that time I had to use a proxy, which made everything complicated and more instable (fortunately since then we use a transparent proxy). Even if I use the Chrome or HTA launcher the encrypted traffic has to go through the SRC server, which can lead to undeterministic or permission denied situations.
My constraints for automated testing with Selenium:
- Separate AUT and TestRunner window
- SSL
- Cross-domain redirects
- Selenese.
Andras
Jun 10, 2008 7:56 PM
darrell esau
darrell esau
"It makes the life of testers, test managers, developers and other people who would have an interest in how the development of a web application is progressing."
It makes the life of these people ___ ?
Easier? Unbearable?
Jun 11, 2008 5:30 AM
Bromine
in response to: darrell esau
Bromine
in response to: darrell esau
Pick one 
Thanks for the correction
Hi,
is there a possibility to run tests via the chrome URL of the IDE (not RC)? If yes, could you please provide a short step-by-step tutorial?
Thanks
Andras