Laravel PHPUnit Testing Issue

if you switch to running your tests using mysqlite, do they complete then?

Hmm... Running now I update the result once its done

HI @automica Sadly it still hangs :(

when it hangs, does it eventually time out? I wonder if you DB is running out of memory at that point.

If you are using RefreshDatabase trait, then try DatabaseMigrations trait instead. Have you changed phpunit.xml to match Laravel6?

The tests are already using DatabaseMigrations only Do you have an example of phpunit.xml for Laravel 6 that i can compare with ?

Check the official repo for it.

https://github.com/laravel/laravel/blob/6.x/phpunit.xml

@kbuczynski is the phpunit.xml for laravel6

<?xml version="1.0" encoding="UTF-8"?>

<phpunit xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

         xsi:noNamespaceSchemaLocation="./vendor/phpunit/phpunit/phpunit.xsd"

         bootstrap="vendor/autoload.php"

         colors="true">

    <testsuites>

        <testsuite name="Unit">

            <directory suffix="Test.php">./tests/Unit</directory>

        </testsuite>



        <testsuite name="Feature">

            <directory suffix="Test.php">./tests/Feature</directory>

        </testsuite>

    </testsuites>

    <filter>

        <whitelist processUncoveredFilesFromWhitelist="true">

            <directory suffix=".php">./app</directory>

        </whitelist>

    </filter>

    <php>

        <server name="APP_ENV" value="testing"/>

        <server name="BCRYPT_ROUNDS" value="4"/>

        <server name="CACHE_DRIVER" value="array"/>

        <server name="DB_CONNECTION" value="sqlite"/>

        <server name="DB_DATABASE" value=":memory:"/>

        <server name="MAIL_DRIVER" value="array"/>

        <server name="QUEUE_CONNECTION" value="sync"/>

        <server name="SESSION_DRIVER" value="array"/>

    </php>

</phpunit>

Thanks @automica @bugsysha I updated the XML just to make sure. sadly it still hangs :(

@kbuczynski Try running phpunit --verbose --debug and see if it provides any additional information

At the very least, it'll show you at what point in your test suite it hangs... or if it hangs at different places, that could be a clue that it's resource exhaustion.

Without codebase it is hard to solve this by guessing.

@bugsysha I agree its is a tough cookie but I would like to know if there is anything I can do on my end to debug this so I can understand why it hangs. something like print out extra msg on the screen or in the log file would be very helpful

@talinon already run using the arguments and i discover that it was hanging on migrate:refresh runned by the DatabaseMigration trait.

@kbuczynski you can use:

       $myDebugVar = array(1, 2, 3);
        fwrite(STDERR, print_r($myDebugVar, TRUE));

to print to console.

I try that thanks :) @automica

You can run tests with ‘vvv’ option to see if it outputs anything useful. Also you can find PhpUnit docs and see logging options there.

Thanks for the help with a debug @automica It showed me what query its failing on

I found out it hangs on (as part of databasemigration trait) drop table "migrations","oauth_auth_codes","oauth_access_tokens","oauth_refresh_tokens","oauth_clients","oauth_personal_access_clients","users","organisation_user","organisations","password_resets","jobs","failed_jobs","roles","abilities","permissions","preferences","assigned_roles","shared_buckets","shared_assets","shared_asset_folders","shared_asset_shared_font","shared_fonts","shared_font_shared_theme","shared_themes","cultures" cascade

and this occurs in dbal package which is at version 2.10.4

Do you have any further tips how to debug this ?

I have debug this further and turns out posgress is locking the transaction casing drop to wait for the release of previous one .

Idk yet how to solve this but at least i got that far

@kbuczynski you may want to look at disabling foreign key constraints when dropping tables.

   Schema::disableForeignKeyConstraints();

you could also look at unlocking the table before dropping it.

   DB::statement('UNLOCK TABLES;');

Small update thanks to @automica i manage to unlock the tables with simple query he gave me as a example. Also manage to determinate which actions cause the lock and fixed it

many thanks <3

@kbuczynski great stuff.