Mobile/Fennec Xpcshell: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
 
(8 intermediate revisions by the same user not shown)
Line 12: Line 12:


==Porting tests to N800==
==Porting tests to N800==
With changes from {{bug|421611}} we have made this process much simpler. 
If following [[Mobile/Build/Fennec#Running Fennec on Maemo|directions]] for running fennec on N800/N810 devices, you will need to package up the tests from the xulrunner directory and the test harness from the source tree:
If following [[Mobile/Build/Fennec#Running Fennec on Maemo|directions]] for running fennec on N800/N810 devices, you will need to package up the tests from the xulrunner directory and the test harness from the source tree:


<pre>
<pre>
cp $(topsrcdir)/testing/xpcshell/* $(xul_objdir)/_tests/
cd $(xul_objdir)
cd $(xul_objdir)/_tests
make package-tests
tar -chf xpcshell.tar xpcshell/ xpcshell-simple/
cd dist
bunzip2 xulrunner-*tests.tar.bz2
scp xulrunner-*tests.tar root@<deviceip>:/media/mmc1
</pre>
</pre>


In addition, we need to copy all the unit/ directories which contain data files, include files and other support scripts. We have developed a script [[http://people.mozilla.org/~jmaher/fennec/xpctest-extract.py xpctest-extract.py]] which will create a xpcfiles.tar for you to copy and untar in the root of your xpcshell test directory
On the device, untar the xulrunner-*tests.tar in your test directory alongside the fennec-*.tar:
 
<pre>
cd /media/mmc1
mkdir unittests
mv fennec-*.tar unittests
mv xulrunner-*tests.tar unittests
cd unittests
tar -xvf fennec-*.tar
tar -xvf xulrunner-*tests.tar
</pre>


Transfer tar files to device via scp and untar it in a _tests/ directory.
In addition (for xpcshell only), we need to move some of the test binaries into the fennec tree:


NOTE: the _tests directory needs to be ../../ from the xulrunner directory.  So if you have a fennec/xulrunner/ directory which contains the xulrunner application, you would need to put the _tests/ folder adjacent to the fennec folder.  This is because some tests like test_extensionmanager reference files in ../../_tests/test_extensionmanager/unit from the appdir.
<pre>
cd /media/mmc1/unittest
cp bin/* fennec/xulrunner
cp bin/components/* fennec/components
cp bin/plugins/* fennec/xulrunner/plugins
</pre>


NOTE: it would be nice if the build script (make) would copy the test harness and support files from the source tree to the xulrunner directory.
==Running the tests==


The tests are normally ran via "make check" from the root of the objdir.  In this case, we are running the tests on the device and there is no source tree.


Make check runs [[http://mxr.mozilla.org/mozilla-central/source/testing/xpcshell/runxpcshelltests.py runxpcshelltests.py]].  We can run this on the Maemo platform like this:


==Running the tests==
<pre>
cd /media/mmc1/unittests
python -u xpcshell/runxpcshelltests.py --xre-path=/media/mmc1/unittests/fennec/xulrunner --manifest=/media/mmc1/unittests/xpcshell/tests/all-test-dirs.list /media/mmc1/unittests/fennec/xulrunner/xpcshell --keep-going
</pre>
 
We have created a framework to wrap the unittests [[Mobile/Fennec_Automation|maemkit]] which makes this a little bit easier.  Keeping the above example, you need to copy the maemkit files to /media/mmc1/maemkit.
 
Now Edit the /media/mmc1/maemkit/maemkit.cfg file:
<pre>
[general]
xre-path = /media/mmc1/unittests/fennec/xulrunner
appname = /media/mmc1/unittests/fennec/fennec
total-clients = 1
client-number = 1
logdir = logs
ostype = linux


The tests are normally ran via "make check" from the root of the objdir. In this case, we are running the tests on the device and there is no source tree.  
[xpcshell]
testroot = /media/mmc1/unittests/xpcshell/tests
utility-path = /media/mmc1/unittests/xpcshell
manifest = /media/mmc1/unittests/xpcshell/tests/all-test-dirs.list
log-file = log_xpcshell.txt
</pre>


Inspecting the test_all.sh script in harness/xpcshell, you can run the test from the command line by doing this:


Run the tests from the directory where you unzipped them like so:
Now execute the tests:
<pre>
<pre>
./run-mozilla.sh xpcshell  -f /media/mmc1/unittests/xpcshell/xpcshell/head.js  -f /media/mmc1/unittests/xpcshell/xpcshell-simple/test_update/unit/test_0051_general.js  -f /media/mmc1/unittests/xpcshell/xpcshell/tail.js  -f /media/mmc1/unittests/xpcshell/xpcshell/execute_test.js
cd /media/mmc1/maemkit
python maemkit-chunked.py --testtype=xpcshell
</pre>
</pre>


This is a cumbersome process, and to make this reasonable, we have created [[http://people.mozilla.com/~jmaher/fennec/xpctests.py xpctest.py]] to run the tests.  This script needs to be edited to point to the xpcshell executable as well as the root of the test harness and test directories.  It will iterate the tests and build up a list of test_ files to run tests against, then run the above command for you.
You can view the results in /media/mmc1/maemkit/log_xpcshell.txt


== TODO's ==  
== TODO's ==  


I will start tracking test failures/bugs [[http://people.mozilla.com/~jmaher/mochitest.htm here]].  This doesn't line up with what is below as there is data from fennec desktop and fennec maemo which adds to the mix.
I will start tracking test failures/bugs [[http://people.mozilla.com/~jmaher/mochitest.htm here]].  This doesn't line up with what is below as there is data from fennec desktop and fennec maemo which adds to the mix.
NOTE: this runs 525 tests where there are 548 tests which run on Firefox (in release only, debug core dumps on assertions at test 223).

Latest revision as of 17:41, 27 March 2009

Getting the Tests

Edit your mozconfig to contain the following lines:

ac_add_options --enable-tests

Get the source and build according to instructions.

to learn more about the tests, visit the [MDC Guide]

Porting tests to N800

With changes from bug 421611 we have made this process much simpler.

If following directions for running fennec on N800/N810 devices, you will need to package up the tests from the xulrunner directory and the test harness from the source tree:

cd $(xul_objdir)
make package-tests
cd dist
bunzip2 xulrunner-*tests.tar.bz2
scp xulrunner-*tests.tar root@<deviceip>:/media/mmc1

On the device, untar the xulrunner-*tests.tar in your test directory alongside the fennec-*.tar:

cd /media/mmc1
mkdir unittests
mv fennec-*.tar unittests
mv xulrunner-*tests.tar unittests
cd unittests
tar -xvf fennec-*.tar
tar -xvf xulrunner-*tests.tar

In addition (for xpcshell only), we need to move some of the test binaries into the fennec tree:

cd /media/mmc1/unittest
cp bin/* fennec/xulrunner
cp bin/components/* fennec/components
cp bin/plugins/* fennec/xulrunner/plugins

Running the tests

The tests are normally ran via "make check" from the root of the objdir. In this case, we are running the tests on the device and there is no source tree.

Make check runs [runxpcshelltests.py]. We can run this on the Maemo platform like this:

cd /media/mmc1/unittests
python -u xpcshell/runxpcshelltests.py --xre-path=/media/mmc1/unittests/fennec/xulrunner --manifest=/media/mmc1/unittests/xpcshell/tests/all-test-dirs.list /media/mmc1/unittests/fennec/xulrunner/xpcshell --keep-going

We have created a framework to wrap the unittests maemkit which makes this a little bit easier. Keeping the above example, you need to copy the maemkit files to /media/mmc1/maemkit.

Now Edit the /media/mmc1/maemkit/maemkit.cfg file:

[general]
xre-path = /media/mmc1/unittests/fennec/xulrunner
appname = /media/mmc1/unittests/fennec/fennec
total-clients = 1
client-number = 1
logdir = logs
ostype = linux

[xpcshell]
testroot = /media/mmc1/unittests/xpcshell/tests
utility-path = /media/mmc1/unittests/xpcshell
manifest = /media/mmc1/unittests/xpcshell/tests/all-test-dirs.list
log-file = log_xpcshell.txt


Now execute the tests:

cd /media/mmc1/maemkit
python maemkit-chunked.py --testtype=xpcshell

You can view the results in /media/mmc1/maemkit/log_xpcshell.txt

TODO's

I will start tracking test failures/bugs [here]. This doesn't line up with what is below as there is data from fennec desktop and fennec maemo which adds to the mix.