Hi Ms2ger, Thanks for calling me on that, just trying to move things along.
Test location and using manifests concepts can also be decoupled. Wherever the location the tests, we will use manifests to define it’s execution. There isn’t really any other way around that. So now the decision is, do we want to: 1. keep external access tests in the same directory as other tests [1] 2. group external access tests into a directory named ‘external’ (e.g. dom/media/tests/mochitest/external/) Many of the QA team believe option #2 is ideal in addition to using manifests to define them. -edwin [1] http://mxr.mozilla.org/mozilla-central/source/dom/media/tests/mochitest/ On Aug 14, 2014, at 12:10 PM, Ms2ger <ms2...@gmail.com> wrote: > Signed PGP part > On 08/14/2014 08:22 PM, Edwin Wong wrote: > > > > I think we're all in agreement. Adding support for manifest and > > mach/make option with the specific directory makes sense. To > > summarize: > > > > * land tests in a directory name "external" so it's easily > > identified as needing external access. > > I don't think anyone is in agreement with this, actually. The > suggestion was to use a manifest annotation *instead of* the > unnecessary directory structure. > > HTH > Ms2ger > > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
