More Travis-CI Testing

[minchinweb]

This is to expand the Travis testing. Specifically, it adds:

• Python 3.8 (on Linux) as an "allowable failure". See Add Python 3.8 support #739. It looks like an easy fix to get this working. Once working, this can removed from the allowable failure list.
• the developmental version of Python (on Linux), as an allowable failure. This is designed as a forward-looking test to help us be aware of anything in the next Python version that might break jrnl. It also has the bonus of helping the Python core devs by exposing the cutting edge Python code to lots of real life Python code.
• a test not in UTC. When I was re-adding the DayOne tests ([Dayone] re-add tests #742), I discovered that the code path changes depending on if the timezone is UTC or now. However, I expect few user's machines are set to UTC, so it seems like an oversight to to only test in UTC.
• MacOS. Because why not? Runs under Python 3.7.4. We have had MacOS-specific bugs in the past (see Update tzlocal #130).
• Windows, as an allowable failure. This is currently tested under Python 3.7, as on Python 3.8 poetry tries to install cryptography as a locally-built wheel (rather than a wheel downloaded from PyPI), which fails. This test currently times out after 10 minutes, as one of the behave steps is to open the editor and get text, and I think it is really opening the editor, rather than pretending to. This is odd, because it doesn't do this on my local machine.... c.f. Windows Support #619

I haven't implemented it here, but the format of Travis should make it simple to add stages to the testing sequence, for example to run all the code through black or check that the dependencies have all been updated.

Checklist

• (n/a) The code change is tested and works locally.
• Tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• Have you followed the guidelines in our Contributing document?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?
• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your core changes, as applicable?

[wren]

This is great! I actually got up early this morning to do this exact thing, only to find you had already done most of it.

Thank you!

[minchinweb]

Glad to help!

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.