-
Notifications
You must be signed in to change notification settings - Fork 9
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
Issue with Pest Architecture Testing after installation #16
Comments
Thx for the feedback! My wife and I are actually in the hospital right now with our newborn, so I can't do anything about this. If there's any possible way that you can figure out why this is happening I can look it over on my phone and merge it though. Is that something you might have the time to do? Edit: I super appreciate you taking the time to make me a repro. 🙏 |
Congratulations! I created a ticket with Pest as I think it's related to that package. If it is indeed something on this package I'll do my best to make a PR to fix it. |
I have a feeling that this is related to #11 By not updating the namespace from my default laravel zero install from |
I'm actually testing this out locally to see if it fixes it. If it does I'll create a PR. I was just going to use Whisky as the root namespace if that is OK with you. |
That's perfect. Thx again for your help |
@ProjektGopher I confirmed that this PR fixes the tests on the sample project using the pest arch plugin. |
That's awesome! I'll look this over in a few and merge it. As soon as I get a chance to open up my laptop, I'll version, build, and publish. Thx so much for taking this one over the finish line. |
After installing this package and setting it up, I'm getting my global architecture tests failing. I get this error:
https://pestphp.com/docs/arch-testing
Here is the whole test:
Prior to whisky install, they all pass:
I created this repo that can be used to replicate the problem:
https://github.com/TappNetwork/whisky-pest
To replicate:
composer install
php artisan test
See the failure.
The text was updated successfully, but these errors were encountered: