Shoudn't beforeApplicationDestroyedCallbacks be called on reverse order when tearing down tests?

[February30th]

I noticed today that laravel calls the teardown callbacks in the same order as they are declared, should't the callbacks be called in reverse order?

As it is if i am using the DatabaseMigrations trait and then add any callback that interacts with the database, the test fails because it can't find any table in the database.