Contrib testing is GREAT.

One of the problems is that core can change, breaking contrib modules. So contrib modules should be tested regularly, and the maintainer should be notified on #fail.

Thanks!

Comments

rfay’s picture

rfay
he,him
Primary language English
Location Palisade, CO, USA
commented
Priority: Normal » Major

Oh I really would like to have this. It's a must for those of us who maintain modules that core can break with its shifts. Already the D8 breakage has started with Examples D8, and reminded me of this sad need.

I'm hoping that we could add this as a capability after we get #1228462: Provide branch testing status and retest options on Drupal.org project pages stabilized and deployed.

catch’s picture

catch
he/him
Primary language English
commented

This would be really useful for entitycache as well, all the entitycache tests are sub-classed core tests with entitycache added to the testing profile - so changes in core code or the tests themselves should directly flag up issues if this is implemented.

drumm’s picture

drumm
he/him
Location NY, US
commented
Issue summary: View changes
Status: Active » Closed (works as designed)

Contrib can now set up daily tests.