-
Notifications
You must be signed in to change notification settings - Fork 207
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
Optional --pest test suite #36
Comments
One thing we're generally trying not to do in this preset is to maintain multiple files that do the same thing, as you can see by the discussion in #12 we'd rather programatically swap things out when we can. If we have to maintain things twice over (2 sets of the same views, 2 sets of the same tests, etc.) it's very easy for things to get out of sync. Do you think this would be achievable with Pest instead of just having a duplicated stubs directory? |
Those are valid concerns indeed. Anyway, shortly after I posted this issue someone undertook an experiment to convert PHPUnit's tests to Pest programmatically, so this might be the ideal solution. |
@alexmartinfr do you happen to know what happened with that experiment to convert PHPUnit tests to Pest and if it's a viable thing to use here? |
@imliam It's still under development at this time, it is technically usable but has some rough edges. It's still too early to include this tool as an automation on your preset though. |
Would you be interested in a
--pest
option which would convert the existing PHPUnit test suite to Pest tests?I'm converting it on my project anyway, and it would be ideal if the work could be reused by others.
The text was updated successfully, but these errors were encountered: