2017 up to now  | 2016 | 2015 | 2014 | 2013 | 2012 | 2011 | 2010 | 2009 | 2008 | 2007

(older archive entries before 2007 are not shown here, but included in the onsite-search)

Mailing List - Entries of 2012


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[QF-Test] Instrumentation of Mozilla Browser


  • Subject: [QF-Test] Instrumentation of Mozilla Browser
  • From: Dennis Page <dnp@?.gov>
  • Date: Fri, 09 Nov 2012 11:52:08 -0800

One of our testers tried to use QFTest to automate the testing of a Browser base application.
He sent me the following email:

To start a Mozilla web browser in QF-Test, the XULRunner is referenced at: /usr/lib/xulrunner-1.9.2
However, in the process of starting the browser, QF-Test attempts to create files under that browser directory, which the testers do not have the permission to do. 
Running out of a copy of the xulrunner-1.9.2 directory, I find that five files are created under the components sub-directory:
·         JSBridge.xpt
·         JSCallback.xpt
·         JSBridge.js
·         xpti.dat
·         compreg.dat


I assume these files are part of QFTest's instrumentation of the browser.

Is it possible to use the browser in /usr/lib (without write permissions) ?

Or do we need to use a copy of the browser which we do have write permission?

Dennis