On Tue, 10 Dec 2013, Nicolas Vigier wrote: > > > In order to help me doing that, I'm very interested to receive from > > > developers of any tor components : > > > > > > - a description or ticket number of bugs that you wish could have been > > > detected earlier with automated tests > > > > https://trac.torproject.org/projects/tor/ticket/8143 comes to mind here. > > Ok. We should soon be able to push tor browser to Mozilla's Try servers, > which will run all the unit tests, so we should be able to detect bugs > like #8143. Regarding this, we will be testing the version that is in tor-browser.git, when a branch receive new commits. In addition to this, an other thing that we could do automatically is rebasing the tor-browser patches onto the unreleased next mozilla esr from http://hg.mozilla.org/releases/mozilla-esr24/ in the default branch. This allows to see in advance if rebasing the patches on the next ESR release will require some work, and if some new Mozilla patches break the build or some tests.
Attachment:
pgp_HgG8Ib_Q_.pgp
Description: PGP signature
_______________________________________________ tor-dev mailing list tor-dev@xxxxxxxxxxxxxxxxxxxx https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev