Testing Firefox Desktop
Which build should I test?
As a localizer you will work against Nightly, which means you should be testing a localized build of Firefox Nightly provided directly by Mozilla.
Why Nightly? Because it’s updated every day, which means that you can fix an error and verify if the correction was effective the day after. It’s definitely a good approach to use this version as your main browser.
At the same time, you, or someone in your team, should be testing also Beta and Release, to make sure updates don’t introduce issues.
How to test
Here are some tips on how to test Firefox once installed in your computer.
Create a new profile
From time to time create a new profile:
- To test that the default searchplugins are still relevant and work as expected.
- To check messages and pages displayed on first run.
- To test dialogs and preferences at the default size.
Search for untranslated strings
- Open all the voices available in the main menu and check that they’re properly localized. If you opted to keep Developer Tools in English, the choice should be consistent across the browser.
- Check the “hamburger” menu for cut strings (unfortunately you’ll need to abbreviate some of them, if they’re not intelligible). Then choose to customize the menu and make sure everything is properly localized.
- Open Preferences/Options and navigate through all tabs, try to open all dialogs like
Exceptions…. Make also sure to select the
Custom settingsoption for History in the Privacy panel.
- Log in with you Firefox Account and make sure that all preferences and dialogs are properly localized.
- Check for untranslated strings and errors in the Library (Bookmarks->View all bookmarks…).
- Open a new Private Window and check the content of the page.
about:supportin the address bar, press Enter, and check for errors or missing translations.
- Check the error pages for malware, unwanted software, deceptive website, harmful website. All strings are also visible in
- Check permissions dialogs on this test website.
- Visit secure and unsecure website, and check the i panel near the URL.
- Right click on a page and verify all panels in the
View Page Infodialog.
Testing webextension permissions dialog
Create a new profile and open
about:config in your browser:
- Right click on the list of available keys and create a new boolean key
- Search for the key
xpinstall.signatures.requiredand set it to
false. This will allow installing unsigned add-ons.
- Open this link, select Download and save the file on your computer.
- Drag the .xpi file on your browser’s window to display the dialog (you don’t need to actually install it).
Test accesskeys and shortcuts
You can test accesskeys only on Windows and Linux, since they’re not available in OS X. If your locale uses a non Latin alphabet and opted to keep the English accesskeys, you don’t have anything to check. If you’re localizing accesskeys, you should check that:
- Accesskeys use letters available in the associated label, and are not displayed between parenthesis at the end of the label itself.
- There are no conflicts, which means there are no items in the same menu or preference panel using the same letter. Starting from Firefox 56, it’s not possible to avoid conflicts in preferences: the guideline in that case is to reduce to a minimum the number of times the same letter is used within a panel.
For shortcuts, you should test at least the most common ones. You should never change a shortcut, unless that combination of keys is not available in the keyboard layout commonly used for your locale. For example, in the Italian keyboard the character
[ is available pressing
è. A shortcut based on
Shift + [ would never work, because it would be read as
Alt + Shift + è.
Test the installer on windows
Download the installer version and make sure that everything is working correctly. In the FTP folder you have both the Full Installer and the Stub Installer (downloading the package from Internet). You should test both at least once.,
Photon is the redesigned UI that will ship in Firefox 57:
- The hamburger menu will be replaced by a static dropdown menu. If you’re on Nightly and still see the old menu, make sure that
browser.photon.structure.enabledis set to
truein about:config (that’s the default value in Nightly 56 and later).
- Test the Overflow menu: the
>>symbol will appear automatically in the main toolbar when resizing the window to a small width. You can then pin an element to it, or add/remove items from the toolbar directly from their context menu.
- Test the onboarding tour by clicking the small fox displayed in the left corner on the New tab. There are also onboarding notifications, displayed at the bottom of the page: you can cycle through them by opening multiple new tabs in a row. Note that the onboarding is currently not compatible with Activity Stream.