With the fix to bug 844288 gtest will also need their own directory. I was planning on allowing users to use <component>/tests folder for their tests but to go in line with this upcoming change I'll update my patches and suggest that anyone who adds gtest to use <component>/tests/gtest to conform with this new style.
I was under the impression this will further recursify our builds making them more expensive. On Wed, Apr 10, 2013 at 3:07 PM, jmaher <joel.ma...@gmail.com> wrote: > There are a couple common directory structures used for storing tests in > the tree: > 1) <component>/tests > 2) <component>/tests/<harness> > > I have a series of patches which will move most of the directory > structures from #1 to a format of #2. This means we would see: > <component>/tests/mochitest > <component>/tests/browser > <component>/tests/chrome > > I have noticed this happens naturally in the newer folders (i.e. > browser/metro). A couple weeks ago I heard a concern this might bitrot > some patches, while that might happen in the last couple weeks only a > handful directories had tests which changed (added/deleted/editing) such > that my patches experienced bitrot. Please comment here or in bug 852065 as > I would like to land these patch this by this weekend. > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
