As shown in #1159 and probably some other issues, testing addons needs some love.
I think it would be good to have our own abstract TestCase for developers to extend that does extra necessary bootstrapping, rather than them needing to extend from Testbench's and do a bunch of wiring.
There's also the ExceptionHandler issue, and Statamic config loading, both of which could probably be done as part of this abstracted class.
There's a bunch of useful fake classes used in our own tests that could be useful to addon devs. Stuff should probably be moved out from our tests directory and into a real Statamic\Testing namespace.
The text was updated successfully, but these errors were encountered:
This issue has not had recent activity and has been marked as stale — by me, a robot. Simply reply to keep it open and send me away. If you do nothing, I will close it in a week. I have no feelings, so whatever you do is fine by me.
As shown in #1159 and probably some other issues, testing addons needs some love.
I think it would be good to have our own abstract TestCase for developers to extend that does extra necessary bootstrapping, rather than them needing to extend from Testbench's and do a bunch of wiring.
There's also the ExceptionHandler issue, and Statamic config loading, both of which could probably be done as part of this abstracted class.
There's a bunch of useful fake classes used in our own tests that could be useful to addon devs. Stuff should probably be moved out from our
tests
directory and into a realStatamic\Testing
namespace.The text was updated successfully, but these errors were encountered: