--
You received this message because you are subscribed to the Google Groups "SilverStripe Core Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to silverstripe-d...@googlegroups.com.
To post to this group, send email to silverst...@googlegroups.com.
Visit this group at http://groups.google.com/group/silverstripe-dev.
For more options, visit https://groups.google.com/d/optout.
I think the majority of problems are surrounding the CMS, the framework itself should be unit testable, and if I'm not mistaken it already is?
--
--
You received this message because you are subscribed to the Google Groups "SilverStripe Core Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to silverstripe-d...@googlegroups.com.
To post to this group, send email to silverst...@googlegroups.com.
Visit this group at http://groups.google.com/group/silverstripe-dev.
For more options, visit https://groups.google.com/d/optout.
The backend testing can ensure things like the API work, but we need to ensure the frontend works too, which again already happens, as Selenium is used to automate frontend testing.
Personally, I don't think the travis configuration is complicated, so I can't see how making it simpler is of any benefit.
Maybe I'm not understanding what you are suggesting, as it is coming across to me that some people are duplicating effort when the functionality already exists to carry out automated testing.
We don't set up a new website every time we want to test what has been worked on, PHPUnit and Behat are already used along with Selenium.
The documentation is old, so you'll have to poke around with the code to see what's already been done, but as I mentioned earlier, pretty much everything that is required to unit test the framework, the CMS, and a project based on using both is already in place. Maybe updating the docs might be a good starting point?