I just posted about a plan to switch the Jetpack tests to be more like the other test suites in the tree including using manifests to define tests ( https://groups.google.com/d/msg/mozilla.dev.tree-management/QquG-CNvmgU/Z8A67brrSjgJ). I'm hitting a problem with our testaddons tests though.
This part of our tests operates on built add-ons. We build them from some source code in the tree then install them in Firefox where they run some tests and report if everything works. It is an important test that code running in an add-on functions correctly. What I want to do is build these add-ons as part of the build process and then reference them in the test manifest. The first part is easy and done, the second part is where I'm stuck because it looks like the manifests all assume that test files are in the source directory. There is generated-files but that is more for support stuff and not for individual tests. So, is supporting tests from the objdir something that would be possible and if so do you have tips on how to go about it? I was considering adding a flag either to DEFAULTS or to every test saying that the test should be found in the objdir instead. This flag would only be needed at build time, once it has been symlinked into _tests the test harnesses can ignore it.
_______________________________________________ dev-builds mailing list dev-builds@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-builds
