Merge OverviewPageTest methods

I know you like merging tests, I prefer having smaller tests, I don't think the time really matters on the testbots, I agree that it can be annoying locally but I never run a full test-class anyway (I comment out the unrelated test methods).

https://www.drupal.org/pift-ci-job/182570

I think its a matter of taste and if you want to do this - it's a perfect novice issue. I'd love more opinions though :)

+1 for merging methods that extend WebTestBase to reduce testing time.

First time for me to modify functional tests in Drupal, so I'm not sure about process and conventions.

I simply replaced public function testMethods with protected function checkMethods, and I created one public function testMethod that merges the four checkMethods. Also, I used comments that were in BackendTestBase for the testFramework method as a model for this merging method.

Is it correct or am I totally wrong?

Since the four methods was merged into one, there was a problem because the first test logout the user, and the remaining tests need to be logged as admin (which was made at the beginning of each test before).

I forgot to make an interdiff for patch #9, sorry for that.

I had to do a change on getTestServer and getTestIndex, because there was an exception saying that the server or the index already exists.

Merging tests is fine to reduce time, but it also implies that the different tests are not independent anymore. In this case:

• After the first test, it is necessary to log again as admin user (because the first one checks permissions and log out then)
• The test server and test index have to be removed before each test (using the same server/index causes problems apparently)