Skip to content
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

Add Test Runner Integration #17

alexfinnarn opened this issue Nov 23, 2016 · 1 comment

Add Test Runner Integration #17

alexfinnarn opened this issue Nov 23, 2016 · 1 comment


Copy link

@alexfinnarn alexfinnarn commented Nov 23, 2016

I know that Backdrop core utilizes a test runner to check pull requests and provide automatic feedback alongside a manual code review. I think Travis CI was used but now it is a different service.

Where I work now, we utilise Travis and Codeclimate for automated reviews, and with the scope of this module, well modules, it would be nice to have that integration to check pull requests against. It would also be nice to have issues add tests in the process of resolving the issue.

I'm mainly asking @jenlampton if there is a typical procedure for Backdrop contrib modules to follow or a link to some FAQ or something?

I will try and follow the example in Backdrop core to set this up.

Copy link

@jenlampton jenlampton commented Nov 23, 2016

edit: Oh, I should start by saying there's no easy flag to 'turn on' to get our test suite running for contrib modules (yet). But I do think there is an issue somewhere requesting something like that, so it may not be far off.

However, it's really easy to run Travis tests on your own fork of whatever project. I do this myself for core work even though Backdrop has switched to Zen CI, because I prefer the reports Travis generates.

Backdrop core switched from Travis Ci to Zen CI because the new Travis infrastructure (at least what's available for FOS projects) was way too slow for us. When they switched off their legacy hardware tests went from finishing in 15 minutes to taking more than 2 hours - exceeding PHP timeout limits, even when we split them across multiple processes.

I'd recommend looking at older versions of backdrop, say 1.2.x, if you want to see what our old travis config file looked like. I'm no expert on how to set such things up. You likely know more than I do!

(I got the tests mostly passing when I set up the new configurations, but really I was just making sure testing would work - and fixing any obvious issues "while I was at it". There are still a few failures that need to be sorted out.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.