Run Simpletests in travisCI

[indigoxela]

Run Simpletests in travisCI

[serundeputy]

@indigoxela ready for review: #31

Run simpletests in CI via lando.

[serundeputy]

we should consider adding a testing badge to the README when/if this is merged

[![Build Status](https://travis-ci.org/backdrop-contrib/i18n.svg?branch=1.x)](https://travis-ci.org/backdrop-contrib/i18n)

[indigoxela]

consider adding a testing badge to the README

Sure, but I still have questions regarding the travis test run.

Why is there a PHP Stack trace?

Why Xenial?

Why all those useless updates (docker, postgres..) of stuff we don't even need? (Or do we need it?)

Why lando? Isn't that overhead?

[serundeputy]

• I don't know anything about a PHP stack trace

  • ahh; i see the PHP stack trace is in the phpcs run output on travis; i think that is php 7.3 complaining about how our old phpcs handles things, but it does not hurt the code linting; we could try building php 7.2, but it doesn't bother me

• Xenial has the version of docker that we want
  we are doing an apt update to make sure we apt install * latest versions of *, but i'm not aware of or seeing updates to postgres (unless they happen in the automatic part of travis which we have no control over)

• lando in CI is pattern we use a lot at my agency, so i'm letting lando/docker set up the tech stack instead of mucking around w/ travis config; so lando matches production, lando runs in CI then deploy to production

  • lando is also how i'm running these tests locally, so know my local runs and CI are the same

[indigoxela]

I don't know anything about a PHP stack trace

I mean that one:

Re lando, composer, xenial... give me some time to think it over. 😉

[indigoxela]

So... I thought it over and gave travisCI a try.

To be honest, I'd actually prefer the way with less overhead (hence shorter time until testbox is up and running).

https://travis-ci.org/github/backdrop-contrib/i18n/builds/683796501

And without exception or traceback.

It turned out, I don't even need drush.