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

SOLR-13592: Introduce EmbeddedSolrTestBase for better integration tests #755

Closed

Conversation

thomaswoeckinger
Copy link
Contributor

To allow better integration of EmbeddedSolrServer, hidden implementation should be moved out of SolrJettyTestBase

@thomaswoeckinger
Copy link
Contributor Author

@gerlowskija plz review

@thomaswoeckinger thomaswoeckinger mentioned this pull request Jul 1, 2019
@thomaswoeckinger
Copy link
Contributor Author

@gerlowskija Any progress on this PR?

@thomaswoeckinger
Copy link
Contributor Author

@gerlowskija Anything new?

@thomaswoeckinger
Copy link
Contributor Author

Need any support, or are you just busy at the moment?

@thomaswoeckinger
Copy link
Contributor Author

Still nothing?

@thomaswoeckinger
Copy link
Contributor Author

@gerlowskija Are you still working on this?

@thomaswoeckinger
Copy link
Contributor Author

Rebased again, @gerlowskija it is two weeks ago since last notice, maybe someone else could takeover the review if jason is to busy?

@thomaswoeckinger
Copy link
Contributor Author

@gerlowskija i saw you are working on other issues too, so i hope you have time to get this PR done, if not so maybe you can hand over to another reviewer.

@gerlowskija
Copy link
Contributor

My apologies Thomas, my gmail filters weren't letting through github notifications and I didn't see this until you pinged me in JIRA.

This all looks good to me, except for the whitespace formatting, which we've talked about on other PRs. Github makes it easy to hide introduction/removal of trailing whitespace, but other changes are harder to hide and make the diff noisier to read and harder to review with confidence: adding "final" modifiers to existing variables, breaking up long method signatures onto multiple lines, etc. Would you mind scrubbing some of those changes from this PR?

In the meantime, I'm going to start "beasting" (run {{ant test-help}} for info) this PR to make sure that none of the affected tests have any flaky failures. I'll comment again in a day or two with some results. (If you want to help out, you can also run some beast-runs if your machine allows it.)

Thanks for your continued patience.

@thomaswoeckinger
Copy link
Contributor Author

thomaswoeckinger commented Aug 12, 2019

My apologies Thomas, my gmail filters weren't letting through github notifications and I didn't see this until you pinged me in JIRA.

:-), no problem, i am still interested to get this in!
Do you know if there are any plans on the master branch migrating to junit 5, this would allow to write tests using default interfaces, so it would be very easy to let them run under different scenarios like embedded, jetty, cloud and so on.

This all looks good to me, except for the whitespace formatting, which we've talked about on other PRs. Github makes it easy to hide introduction/removal of trailing whitespace, but other changes are harder to hide and make the diff noisier to read and harder to review with confidence: adding "final" modifiers to existing variables, breaking up long method signatures onto multiple lines, etc. Would you mind scrubbing some of those changes from this PR?

Yes we talked about, my point: why using common format rules if even no one is using them.
But anyway, i can take a look at the method signatures, if you like, but i think it is not that difficult to review at the current state.

In the meantime, I'm going to start "beasting" (run {{ant test-help}} for info) this PR to make sure that none of the affected tests have any flaky failures. I'll comment again in a day or two with some results. (If you want to help out, you can also run some beast-runs if your machine allows it.)

Thanks for your continued patience.

i will have a look at it, the default test are all running on my site, i will comment on this PR when i have results.

And you are very welcome with your comments and suggestions!

@thomaswoeckinger
Copy link
Contributor Author

Did not had time to test yet, i am at vacation for the next to week, than i can continue to work on it.

@gerlowskija
Copy link
Contributor

I haven't heard anyone bring up JUnit 5, no. We'll have to do it eventually, but it could potentially be a massive change for Solr, so my guess is that no one will push for it until they absolutely have to.

@gerlowskija
Copy link
Contributor

Is there any difference between LargeVolumeEmbeddedTest, LargeVolumeJettyTest, and LargeVolumeBinaryJettyTest? It looks like all three are exactly the same with this PR. They look suspiciously similar before this PR too, so I think the problem pre-exists this change. But it's still very odd. Just wondering if you dug into that at all as you were working?

@asfgit asfgit closed this in 319cb00 Aug 29, 2019
@thomaswoeckinger thomaswoeckinger deleted the embedded_test_base branch August 31, 2019 22:53
@thomaswoeckinger
Copy link
Contributor Author

Is there any difference between LargeVolumeEmbeddedTest, LargeVolumeJettyTest, and LargeVolumeBinaryJettyTest? It looks like all three are exactly the same with this PR. They look suspiciously similar before this PR too, so I think the problem pre-exists this change. But it's still very odd. Just wondering if you dug into that at all as you were working?

They are using old init from my point of view, all other Jetty tests are using initCore().

@thomaswoeckinger
Copy link
Contributor Author

Any plans on merging this back to 8.x?

@thomaswoeckinger
Copy link
Contributor Author

I will close the coresponding issue now.

@dsmiley
Copy link
Contributor

dsmiley commented Sep 3, 2019

Note that the javadocs on org.apache.solr.SolrJettyTestBase#createNewSolrClient is obsolete as it still references using an "embedded implementation" which is no longer true.

@thomaswoeckinger
Copy link
Contributor Author

Note that the javadocs on org.apache.solr.SolrJettyTestBase#createNewSolrClient is obsolete as it still references using an "embedded implementation" which is no longer true.

I will remove the reference in the followup PR #665 .

asfgit pushed a commit that referenced this pull request Oct 8, 2019
This groundwork commit allows tests to randomize request content-type
more flexibly.  This will be taken advantage of by subsequent commits.

Co-Authored-By: Thomas Woeckinger
Closes: #755
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants