Le 07/03/2014 02:29, Jon Robson a écrit : > 2 problems here - tests run only for the extension the code touches > and currently browser tests only run after as these are slow and > people would be annoyed if code took 20 minutes to merge. We've had > issues in the past where changes in VisualEditor have broken things in > MobileFrontend that trigger failed tests. Maybe core should run all > browser tests for all deployed extensions as part of the merge process > to avoid this?
Hello, Indeed, we need more integration tests when gating changes in mediawiki/core. At a minimal: run unit tests from all the extensions which are deployed. Would be nice to run the QUnit tests as well. Right now the core changes only run core tests and extensions do not even run the core one. As for changes taking 2 hours to be merged, I don't think it is a problem as long as we can skip the gate entirely in case of emergency. Which we could do by adding live hack on the site :-] And we need integration tests for the wmf branches! -- Antoine "hashar" Musso _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
