Dan and Andreas bring up points that I was going to add, but to further it a bit more:
Running tests in the correct real environment is important and I think we'd have to be very cautious of running tests in headless mode only. I see headless more as a complimentary testing mode, where you have 99% of the guts of Firefox, but a much nicer workflow for testing. I'm hoping with headless Firefox and headless Chrome it will be much easier for developers to run test suites in these environments where the browser is much closer to the real thing as opposed to something like PhantomJS or just testing a node environment. On Fri, Jun 16, 2017 at 6:22 AM, Ehsan Akhgari <ehsan.akhg...@gmail.com> wrote: > On 06/15/2017 04:37 PM, Nathan Froyd wrote: > >> On Thu, Jun 15, 2017 at 2:02 PM, Brendan Dahl <bd...@mozilla.com> wrote: >> >>> Headless will run less of the platform specific widget code and I don't >>> recommend using it for platform specific testing. It is targeted more at >>> web developers and testing regular content pages. There definitely will >>> be >>> cases where regular pages will need to exercise code that would vary per >>> platform (such as fullscreen), but hopefully we can provide good enough >>> emulation in headless and work to have a consistent enough behavior >>> across >>> platforms that it won't matter. >>> >> Would it be feasible to use headless mode for mochitests (or reftests, >> etc. etc.)? >> > Running the tests that we rely on for correctness on an environment that > looks this different than the environment that our users run sounds like a > bad thing to do. What would be the advantage of doing so? > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
