Hi All, We currently have 10 C++ GTest unittests in Firefox in media/mtransport/test and media/webrtc/signaling/test that build standalone tests with the FF build. These tests currently run as part of the build and make the B orange if they fail which is why a couple of them are still stubbed at runtime based on an environment variable.
I am looking into getting them to build on Windows (Bug 862837). This appears non-trivial because of the different way the Windows build links. It was suggested by Ted that we move them to the new firefox GTest which would build them only with --enable-gtest and run as part of 'firefox -unittest'. So, for those of you interested, my questions are: 1. If they were moved into the standard Gtest, would they still be built by tbpl and run with the tests instead of as part of the build? 2. One of them in particular (signaling_unittest) is fairly large and takes minutes to run. Should it be run separately by using GTEST_FILTER? 3. Any other reasons you think this might be a terrible idea? -EH _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
