(replies inline) On Thu, 28 Sep 2017, Jesse Glick wrote:
> After the fiasco of Jenkins 2.80 some of us have been discussing ways > to speed up `acceptance-test-harness` to the point where it would be > practical to run all or part of it against core more frequently, > perhaps even in core PR builds. > > Part of the problem is that the test infrastructure has a ton of > overhead. One suggestion was to use PhantomJS rather than a live > browser like Firefox during typical test runs. I suggested optimizing > the plugin upload mechanism in `LocalController`, perhaps using a mock > local update center URL to avoid network downloads (as well as > simplifying the way `LOCAL_JARS` and similar options work). Just an FYI on this point, I have been working on upgrading to Selenium 3.6.0 (https://github.com/jenkinsci/acceptance-test-harness/pull/360) which introduces support for newer browsers (duh) which include headless modes. I will be investigating other test speed up options after that, but I fully support jglick's approach of deleting pointless/unnecessary test cases. Fastest Selenium test is one which isn't executed :P - R. Tyler Croy ------------------------------------------------------ Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> xmpp: [email protected] % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F ------------------------------------------------------ -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/20170928154616.euvxvuar4qbuqir7%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: PGP signature
