every time we change a component we make sure the test cases for it
pass
but often times there might be some unforeseen consequences for the
output in the views.
i was wondering how this could me automated
ideas:
- level 1: build a crawler and index all available views and test them
for errors, warnings, ...
- level 2: add specific urls not reachable by the crawler
- level 3: add manual test cases for backend (logged in)
every time we update the live branch we run the web test
what do you think? a coverage of 99% for all sites checking for any
errors and warnings would be a huge help
we could index all urls in a table
by using some custom HtmlHelper::url() we could save all generated
urls in this table automatically (saves some crawling time).
if we save the differences between tests we could even evaluate those
differences compared to the errors occuring etc
the biggest problem as of right now is a suitable crawler...
the ones i tried seem not to fit to the framework
Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions.
You received this message because you are subscribed to the Google Groups "CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
No comments:
Post a Comment