You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I use expect($someEntity)->not->toBeNull() I'm noticing significant performance issues. I'm running "integration" tests with symfony and doctrine and asserting on doctrine entities. In some cases using not->toBeNull() will take upwards of 40s and removing it can reduce it to ~10s.
What Happened
When I use
expect($someEntity)->not->toBeNull()
I'm noticing significant performance issues. I'm running "integration" tests with symfony and doctrine and asserting on doctrine entities. In some cases usingnot->toBeNull()
will take upwards of 40s and removing it can reduce it to ~10s.How to Reproduce
In a symfony application, write a pest test that extends symfonys BaseWebTestCase (docs here https://symfony.com/doc/current/testing.html#write-your-first-application-test) and write a test that asserts a doctrine entity exists.
Sample Repository
No response
Pest Version
2.31.0
PHP Version
8.2.15
Operation System
Linux
Notes
No response
The text was updated successfully, but these errors were encountered: