Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Performance issue with ->not->toBeNull() #1137

Open
cborgas opened this issue Apr 15, 2024 · 0 comments
Open

[Bug]: Performance issue with ->not->toBeNull() #1137

cborgas opened this issue Apr 15, 2024 · 0 comments
Labels

Comments

@cborgas
Copy link

cborgas commented Apr 15, 2024

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 using not->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

@cborgas cborgas added the bug label Apr 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant