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
SOLR-13592: Introduce EmbeddedSolrTestBase for better integration tests #755
Conversation
@gerlowskija plz review |
@gerlowskija Any progress on this PR? |
a6c8e95
to
ab53638
Compare
@gerlowskija Anything new? |
Need any support, or are you just busy at the moment? |
Still nothing? |
@gerlowskija Are you still working on this? |
ab53638
to
9b579f2
Compare
Rebased again, @gerlowskija it is two weeks ago since last notice, maybe someone else could takeover the review if jason is to busy? |
@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. |
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. |
:-), no problem, i am still interested to get this in!
Yes we talked about, my point: why using common format rules if even no one is using them.
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! |
Did not had time to test yet, i am at vacation for the next to week, than i can continue to work on it. |
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. |
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(). |
Any plans on merging this back to 8.x? |
I will close the coresponding issue now. |
Note that the javadocs on |
I will remove the reference in the followup PR #665 . |
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
To allow better integration of EmbeddedSolrServer, hidden implementation should be moved out of SolrJettyTestBase