Confirmed users
3,376
edits
Mobile/Fennec Chrome: Difference between revisions
Jump to navigation
Jump to search
→Running Chrome tests on Fennec
| Line 41: | Line 41: | ||
Chrome tests are run just like mochitests except they have the --chrome flag set on the command line when launching. | Chrome tests are run just like mochitests except they have the --chrome flag set on the command line when launching. | ||
<pre> | |||
python /media/mmc1/unittests/mochitest/runtests.py --autorun --close-when-done --chrome --utility-path=/media/mmc1/unittests/bin --appname=/media/mmc1/unittests/fennec/fennec --xre-path=/media/mmc1/unittests/fennec/xulrunner --certificate-path=/media/mmc1/unittests/certs --log-file=logs/log_content.txt | |||
</pre> | |||
The Chrome tests will fail when run on a device. This is because we don't have enough memory available to load the whole set of tests into memory and execute. | |||
To work around this, we run a subset of tests at a time. We have found that running one subdirectory under the chrome/ folder works out well. Once we have a --test-path that works for directories in chrome, we can do this easier. At the moment, we remove all files from the chrome/ directory and move the files over one directory at a time: | |||
<pre> | <pre> | ||
cd | cd /media/mmc1/unittests/mochitest | ||
cp -R chrome chrome.bak | cp -R chrome chrome.bak | ||
| Line 53: | Line 56: | ||
rm -Rf chrome/* | rm -Rf chrome/* | ||
cp -R chrome.bak/content chrome/ | cp -R chrome.bak/content chrome/ | ||
</pre> | </pre> | ||
== TODO == | == TODO == | ||