Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WIP Speed up integration tests and fail faster #7024

Closed
wants to merge 13 commits into from

Conversation

spalger
Copy link
Contributor

@spalger spalger commented Apr 22, 2016

This switches to use chrome for the integration tests, which has proven to give much better performance rendering Kibana.

It also turns on the new bail option available in version 3.1 of intern. This option will skip any test after a failed one.

Both of these changes are intended to improve performance of the integration tests since they are currently taking close to 15 minutes to run.

@spalger spalger changed the title Speed up integration tests and fail faster WIP Speed up integration tests and fail faster Apr 22, 2016
@spalger spalger force-pushed the implement/interBailBehavior branch 2 times, most recently from 246c59f to 9e80f03 Compare April 22, 2016 16:15
@spalger spalger force-pushed the implement/interBailBehavior branch 5 times, most recently from 7a4e854 to 7ebbfe0 Compare April 22, 2016 19:01
The `common.log` and `common.debug` API currently accept a single string arguments, which is similar to the console.log API but not complete.

This simple change brings updates it to match the API completely, supporting things like multiple arguments and sprintf-style templates.
@spalger spalger force-pushed the implement/interBailBehavior branch 3 times, most recently from b09ad2b to 7230045 Compare April 22, 2016 19:53
@spalger spalger force-pushed the implement/interBailBehavior branch from 5104c68 to 03ea7db Compare April 22, 2016 20:39
@LeeDr
Copy link

LeeDr commented Jun 10, 2016

@spalger Did you stop on this for some reason? Was there another issue or PR for switching to Chrome browser? If not, I could pick this up.

The urgency for this just went up this week because of Firefox 47 release. According to SeleniumHQ/selenium#1862 we have to switch from the FirefoxDriver driver to Marionette. I've made some progress towards that, but not working yet.

@spalger
Copy link
Contributor Author

spalger commented Jun 10, 2016

I don't recall precisely. I can take a look later today but I feel like this was basically ready to go.

@LeeDr
Copy link

LeeDr commented Jun 13, 2016

jenkins, test it

@LeeDr LeeDr self-assigned this Jun 13, 2016
LeeDr pushed a commit to LeeDr/kibana that referenced this pull request Jun 13, 2016
@LeeDr
Copy link

LeeDr commented Jun 14, 2016

Re-implementing in #7442

@LeeDr LeeDr closed this Jun 14, 2016
LeeDr pushed a commit that referenced this pull request Jun 17, 2016
Re-implement most of PR #7024 switch to Chrome browser
airow pushed a commit to airow/kibana that referenced this pull request Feb 16, 2017
Re-implement most of PR elastic#7024 switch to Chrome browser

Former-commit-id: e2ff6bb
@spalger spalger deleted the implement/interBailBehavior branch October 18, 2019 17:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants