At first we would advise you to check if the „Directory of Mozilla Installation“ property in your „Start/Open Browser“ node points to a valid Mozilla/Seamonkey/Firefox installation.
If the property already points to a valid installation or after fixing it you still get the error message you should check how your Mozilla/Seamonkey/Firefox browser was installed. There are differences in the GRE-Path handling for older Mozilla versions (Mozilla version 1.8 and older, Seamonkey version older than 1.1.0) depending on the source of installation.
- SeaMonkey < V1.1.0 or Mozilla <= V1.8 was installed with the official installer provided by mozilla.org. In this case the Mozilla GRE files and the Mozilla Chrome files are stored in different directories.
It is necessary to copy the Mozilla Chrome files (the complete directory) in the Mozilla GRE directory.
- Mozilla chrome files are stored in your Mozilla/Seamonkey installation directory for example: C:\Program Files\seamonkey\chrome
- the Mozilla GRE directory can also be found in your Mozilla/Seamonkey installation directory (c:\Program Files\Common Files\mozilla.org\GRE\[GRE_VERSION]) for example:
C:\Program Files\Common Files\mozilla.org\GRE\1.8.0.12_2007051005
- Seamonkey < V1.1.0 or Mozilla <= V1.8 was unpacked from a ZIP file.
In this case it is sufficient to set the used installation directory as the „Directory of Mozilla Installation“ property.
It seems like you have configured a standard Firefox 1 or Firefox 2 as browser engine for web2test. We suggest the usage of Firefox 3 instead.
For further information please have a look at „Why doesn’t web2test work with the standard Firefox 2 browser? (the difference between Seamonkey 1.x and Firefox 2.x)“ in this FAQ.
Generally web2test works with all Mozilla based browsers from version 1.8, especially Seamonkey from version 1.0 and Firefox from Version 1.5.
All these browsers are based on the same source code. There is no difference on the inbuilt JavaScript engine and the rendering of HTML in regard to the browser compatibility. As a consequence, there should be no need to use Firefox.
One significant difference between these browsers is that Firefox 2 is a special, optimized version with statically linked libraries. However in Seamonkey all libraries are dynamically linked.
As web2test encapsulates the installed browsers, all browser components are linked dynamically during the runtime. If a browser has no modular components, such as Firefox, there is no possibility for embedding such a browser.
Besides, there is also a way to support Firefox 2 in web2test, if you can do an own build of a dedicated Firefox version with the usage of a special compiler option.
See also:
Mozilla Developer Center
Accordingly, a specially built version of Firefox 2.0.0.12 is available for download here:
Download Firefox build with dynamically linked libraries
Firefox 3 ships with a private XULRunner package. That will offer the possibility to embed a standard Firefox without additional expenditure. For this reason the former restrictions of Mozilla support omit SeaMonkey or an own dynamically linked build of Firefox.
First of all, check your options within web2test:
Edit > Options > Replay > Events Activate SUT windows automatically - Checked
Then, you can set an option to “Minimize test-suite window during replay,” but this should be the last resort, since you also want to watch the program flow:
Edit > Options > Replay > Minimize test-suite window during replay - Checked
If the problem still occurs please check your Windows-Registry settings:
What you are seeing is the effect of a Windows “feature” that prevents applications from coming to the front and stealing the focus from your currently active window. Although this feature is useful in day-to-day work, it causes problems with test automation. Luckily, web2test is able to inject events into browser windows that are in the background; otherwise the problem would be severe.
Still, testing becomes more convenient and in some special cases (Image-Checks, hard events) more robust if Windows is told to allow applications to bring their windows to the foreground as required.
To do so, run < regedit > and edit the key:
HKCU\Control Panel\Desktop\ForegroundLockTimeout
and set its value to 1 (not 0). Alternatively you can use Tweak-UI and change the setting for “Prevent applications from stealing focus”.
Unfortunately, you need to log out for the value to become effective, otherwise web2test could change it on the fly.
For further information see also:
New program window appears behind all other open windows on a Windows 2000-based, Windows XP-based, Windows Server 2003-based, or Windows Vista-based computer
Based on:
qfs.de/faqThis problems occurs because web2test is trying to copy some specific Javscript bridge files inside the directory of the browser you defined for testing.
Microsoft Windows Vista and Linux systems have some security restrictions which prohibit those actions inside of some directories.
To work around this problem you need to start web2test as administrator.
The copied files will be removed when you close your web2test browser engine.
