The Tor Browser Bundle [https://blog.torproject.org/blog/volunteer-qa-price-freedom-eternal-vigilance Volunteer QA] process is managed by Runa A. Sandvik.
To participate in the process, subscribe to the [https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-qa tor-qa mailinglist]. Subscription is moderated, and you'll have to provide your platform information (or at least commit to collecting or writing tests) to Runa to participate, and discussion is restricted to commenting on specific releases and test suite development.
Do not mix test suite development discussion in release test result threads. We want to keep the release threads clean to easily check for regressions from release to release. Replying to test results to mention test page issues, known bugs, or to announce the filing of new bugs are perhaps the lone exceptions here.
If you want to simply view the action, the [http://lists.torproject.org/pipermail/tor-qa/ mailing list archives] are public.
= The Process =
The process itself works as follows: Runa will send out a mail with a url to a set of builds with a time limit for feedback using the Functionality Checklist below. The length of the time limit will depend upon the release branch and the reasons for the release. If serious issues specific to that release are found, the build may be rejected. In all other cases, the build will be published upon expiry of the time limit, regardless of who actually tests it or replies.
We want both positive and negative feedback in the release thread, as well as specific information about your OS and its version, CPU, and any antivirus, firewall, or sandboxing software you use, as well as the version for that. We want this information so we can check for regressions, so that we know the last successfully tested build for a given platform.
However, remember we want to keep the build test result threads focused on results, and not discussion.
= Documentation Checklist =
1. Check that the version number on the top line of the changelog file matches the version number in the filename (to prevent things #6084).
= Functionality Checklist =
1. TBB Launches successfully
1. Connects to the Tor network
1. Browser toolbars and menus work. Tab dragging works.
1. All extensions are present and functional
1. Web browsing works as expected. See Test Pages.
== Test Pages to Use ==
FIXME: At some point we should differentiate this into a "short list" for security and/or minor releases, and the "Full List" for the alpha releases.
{{{#!comment
1. https://www.torproject.org/projects/torbrowser/design/#Testing and sub-pages
* May need updating and trimming to key tests. We're open to suggestions!
}}}
1. http://samy.pl/evercookie
* Use Torbutton's 'New Identity' to clear them, and make sure they're gone.
1. Test out the OS X Sandbox on OS X 10.7. Watch your logs.
* https://romab.com/tbb/
}}}
1. Someone should upload all binaries inside at least the Windows bundles, including the "installer" itself, at https://www.virustotal.com/en/ so we don't again get floods of false positives.
