mirror of
https://github.com/silverstripe/silverstripe-cms
synced 2024-07-01 00:49:26 +02:00
ed8ee4e9b8
The problem is FulltextSearchable::enable() does two things: It enables the extension, as well as sets the MySQL create table option to MyISAM. Later tests run with the extension enabled, because it doesn't get removed at the end of the test, but the table type is set back to InnoDB when the test is reset and schema recreated. This produces side-effects where later tests in a suite tries to run ALTER TABLE on File and add fulltext indexes when the table type is set to InnoDB, causing an error.
35 lines
1.0 KiB
PHP
35 lines
1.0 KiB
PHP
<?php
|
|
class ContentControllerSearchExtensionTest extends SapphireTest {
|
|
|
|
public function testCustomSearchFormClassesToTest() {
|
|
$page = new Page();
|
|
$page->URLSegment = 'whatever';
|
|
$page->Content = 'oh really?';
|
|
$page->write();
|
|
$page->publish('Stage', 'Live');
|
|
$controller = new ContentController($page);
|
|
$form = $controller->SearchForm();
|
|
|
|
if (get_class($form) == 'SearchForm') $this->assertEquals(array('File'), $form->getClassesToSearch());
|
|
}
|
|
|
|
public function setUpOnce() {
|
|
parent::setUpOnce();
|
|
|
|
FulltextSearchable::enable('File');
|
|
}
|
|
|
|
/**
|
|
* FulltextSearchable::enable() leaves behind remains that don't get cleaned up
|
|
* properly at the end of the test. This becomes apparent when a later test tries to
|
|
* ALTER TABLE File and add fulltext indexes with the InnoDB table type.
|
|
*/
|
|
public function tearDownOnce() {
|
|
parent::tearDownOnce();
|
|
|
|
Config::inst()->update('File', 'create_table_options', array('MySQLDatabase' => 'ENGINE=InnoDB'));
|
|
File::remove_extension('FulltextSearchable');
|
|
}
|
|
|
|
}
|