PDO does not support :memory:$ PDO=1 DB=SQLITE vendor/bin/phpunit -d memory_limit=512M vendor/silverstripe/framework/tests/ --stop-on-error
Get the PID: sudo iotop
1) SilverStripe\ORM\Tests\DataListTest::testAggregateFilters
Failed asserting that actual size 0 matches expected size 1.
On the down side, that test is super helpful with its assertion comments;
$this->assertCount(1, ...); appears 7 times.
A little unsettling:
PDO just saw the tests stall at 85% while I was typing this. Had to ^C to exit.
~Other~ Travis problems
The test suite does not run from memory.
It seems like it will, and it probably does when run from a project (e.g. added as a requirement to installer).
Except travis, because the module is the app, not in vendor/ during a travis test.
This seems insignificant, except that I see differences in results when running from memory:
8) SilverStripe\Forms\Tests\NumericFieldTest::testSetSubmittedValue with data set #28 ('fr_FR', 1, '15.000,5', 15000.5, '15 000,5')
Expected input 15.000,5 to be cleaned up as 15 000,5 in locale fr_FR
Failed asserting that two strings are equal.
--- Expected
+++ Actual
@@ @@
-'15 000,5'
+'15 000,5'
I suspect it's to do with character encoding.
It's always NumericField, and always the locale adaptation business.
This could be setup related (environmental), but should be looked into. Can anyone else replicate?
git clone git@github.com:silverstripe/silverstripe-sqlite3
cd silverstripe-sqlite3
git checkout 2
composer install
Quick memory shim for testing (in a travis-esque manner):
The Travis setup denotes that we install recipe-cms - however we only ever run the framework tests. Could it not become recipe-core, or simply framework itself?
I'm not sure of the impact the presence of extra modules will have on the time it takes to test, is it even worth looking into?
Thinking about composer install time & manifest creation time
PDO Problems
PDO does not support
:memory:
$ PDO=1 DB=SQLITE vendor/bin/phpunit -d memory_limit=512M vendor/silverstripe/framework/tests/ --stop-on-error
Get the PID:sudo iotop
Cool filename :/
PDO causes the last remaining red spot on the test suite https://travis-ci.org/silverstripe/silverstripe-sqlite3/builds/443601934
On the bright side, it's only a single test.
On the down side, that test is super helpful with its assertion comments;
$this->assertCount(1, ...);
appears 7 times.A little unsettling: PDO just saw the tests stall at 85% while I was typing this. Had to
^C
to exit.~Other~ Travis problems
The test suite does not run from memory. It seems like it will, and it probably does when run from a project (e.g. added as a requirement to installer). Except travis, because the module is the app, not in
vendor/
during a travis test.This seems insignificant, except that I see differences in results when running from memory:
I suspect it's to do with character encoding. It's always NumericField, and always the locale adaptation business.
This could be setup related (environmental), but should be looked into. Can anyone else replicate?
Quick memory shim for testing (in a travis-esque manner):
DB=SQLITE vendor/bin/phpunit -d memory_limit=512M vendor/silverstripe/framework/tests/ --stop-on-error
General observation
The Travis setup denotes that we install
recipe-cms
- however we only ever run theframework
tests. Could it not becomerecipe-core
, or simplyframework
itself? I'm not sure of the impact the presence of extra modules will have on the time it takes to test, is it even worth looking into? Thinking about composer install time & manifest creation time